U0880 Community Continuous Improvement Planner

Community Continuous Improvement Planner

Why This Skill Exists

We need this skill because real-world feedback loops are necessary for continuous alignment. This specific skill turns findings into sustained upgrade cycles.

When To Use

Use this skill when the request explicitly needs "Community Continuous Improvement Planner" outcomes in the Community Engagement and Feedback domain.

Step-by-Step Implementation Guide

1. Define the scope and success metrics for Community Continuous Improvement Planner, including at least three measurable KPIs tied to community trust loss and unaddressed concerns.
2. Design and version the input/output contract for feedback channels, sentiment, urgency, and follow-ups, then add schema validation and failure-mode handling.
3. Implement the core capability using closed-loop prioritization, and produce improvement roadmaps with deterministic scoring.
4. Integrate the skill into swarm orchestration: task routing, approval gates, retry strategy, and rollback controls.
5. Add unit, integration, and simulation tests that explicitly cover community trust loss and unaddressed concerns, then run regression baselines.
6. Deploy behind a feature flag, monitor telemetry/alerts for two release cycles, and iterate thresholds based on observed outcomes.

Required Deliverables

• Capability contract: input schema, deterministic scoring, output schema, and failure modes.
• Runtime profile: planning-router using closed-loop prioritization to produce improvement roadmaps.
• Orchestration integration: community-engagement-and-feedback:planning-router routing, approval gates, retries, and rollback controls.
• Validation evidence: unit, integration, simulation, regression-baseline suites and rollout telemetry.

Operational Runbook

Preflight

• Confirm the Community Continuous Improvement Planner request scope, source evidence, and measurable success criteria before execution.
• Verify feature flag skill_0880_community-continuous-improvement, approval gates, and rollback owner before autonomous use.

Execution

• Execute closed-loop prioritization with deterministic scoring and reproducible trace capture.
• Produce improvement roadmaps plus scorecard, assumptions, and unresolved-risk notes.

Recovery

• Fail closed when required signals, evidence, or approval gates are missing.
• Rollback to the last stable baseline when posture is critical or validation fails.

Handoff

• Publish improvement roadmaps, validation evidence, and telemetry links to downstream owners.
• Queue follow-up tasks for unresolved risks, threshold tuning, or approval review.

Guardrails

• [quality] Require deterministic scoring and validation evidence before promotion.
• [reliability] Preserve retries, rollback controls, and failure-mode evidence for every run.
• [safety] Route critical posture or missing approval gates to human review before autonomous action.