Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

sei-analytics

Sterne60

Forks11

Aktualisiert22. Mai 2026 um 19:02

Advanced engineering analytics via Harness Software Engineering Insights (SEI) MCP. Configure sprint velocity and estimation accuracy tracking, engineering investment allocation breakdowns, sprint planning with capacity forecasts, and release readiness assessments. Use when asked about sprint analytics, investment allocation, sprint planning, capacity forecasting, or release readiness. Do NOT use for DORA metrics (use dora-metrics instead). Trigger phrases: sprint velocity, sprint analytics, investment allocation, capacity planning, sprint forecast, release readiness, engineering productivity, estimation accuracy, sprint planning, scope creep, code quality trends.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

harness

harness/harness-skills

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	sei-analytics
description	Advanced engineering analytics via Harness Software Engineering Insights (SEI) MCP. Configure sprint velocity and estimation accuracy tracking, engineering investment allocation breakdowns, sprint planning with capacity forecasts, and release readiness assessments. Use when asked about sprint analytics, investment allocation, sprint planning, capacity forecasting, or release readiness. Do NOT use for DORA metrics (use dora-metrics instead). Trigger phrases: sprint velocity, sprint analytics, investment allocation, capacity planning, sprint forecast, release readiness, engineering productivity, estimation accuracy, sprint planning, scope creep, code quality trends.
metadata	{"author":"Harness","version":"1.0.0","mcp-server":"harness-mcp-v2"}
license	Apache-2.0
compatibility	Requires Harness MCP v2 server (harness-mcp-v2)

SEI Analytics

Configure sprint analytics, investment allocation, capacity forecasting, and release readiness assessments in Harness Software Engineering Insights.

Instructions

Step 1: Establish Scope

Confirm the user's org, team, and tracking period.

Call MCP tool: harness_list
Parameters:
  resource_type: "project"
  org_id: "<organization>"

Step 2: Identify the SEI Task

Determine which analytics the user needs:

Sprint Analytics -- Velocity, estimation accuracy, scope change tracking
Investment Allocation -- Engineering time breakdown by category
Sprint Planning and Capacity Forecast -- Data-driven sprint planning
Release Readiness Assessment -- Checklist for release go/no-go

Step 3: Configure Sprint Analytics

Gather from the user:

Team name and sprint length (weeks)
Tracking period (last N sprints)
Issue tracker integration (Jira, Azure DevOps, Linear)

Analyze sprint metrics:

Velocity:

Story points committed vs. completed per sprint
Velocity trend over the tracking period
Carryover rate (% of stories that spill into next sprint)

Estimation Accuracy:

Actual vs. estimated story points across sprints
Which issue types are consistently underestimated
Estimation accuracy trend (improving or degrading)

Scope Change:

Stories added mid-sprint (scope creep %)
Stories removed mid-sprint
Net scope change and its impact on completion rate

Delivery Composition:

Breakdown by issue type: features, bugs, tech debt, maintenance
Breakdown by priority: P0/P1 vs. lower priority
Team-level vs. individual-level trends

Step 4: Analyze Investment Allocation

Gather from the user:

Teams to analyze
Time period for analysis
Investment categories (features, bugs, tech debt, maintenance, ops)

Calculate allocation:

% of engineering time per category
Compare against target allocation (e.g., 70% features, 15% tech debt, 10% bugs, 5% ops)
Trend over time: is tech debt growing or shrinking?
Per-team breakdowns to identify teams disproportionately spending on bugs or ops

Present with:

Current allocation vs. target allocation
Recommendations for rebalancing
Impact of current allocation on velocity and quality trends

Step 5: Sprint Planning and Capacity Forecast

Gather from the user:

Sprint number, duration, and team size
Planned PTO, meetings, and other commitments

Calculate capacity:

Available engineering days = team size * sprint days - PTO - meeting overhead
Historical velocity per engineer per sprint
Recommended story points for the sprint (based on rolling average)

Risk factors to flag:

Large stories (>8 points) that could block the sprint
Dependencies on other teams
Carryover from previous sprint
Tech debt items that may slow feature work

Step 6: Release Readiness Assessment

Gather from the user:

Service name, version, target environment
Change summary and target release date

Assess readiness:

Code Quality:

Code coverage delta (current vs. threshold)
Static analysis findings (new warnings or errors)
Code review completion (all PRs reviewed and approved)

Pipeline Health:

Call MCP tool: harness_list
Parameters:
  resource_type: "execution"
  org_id: "<organization>"
  project_id: "<project>"

CI pipeline pass rate for the release branch
All required stages green (build, test, security, integration)

Testing:

Unit test pass rate and coverage
Integration test results
Performance test results vs. baseline

Security:

No unresolved critical or high CVEs
Security scan completed and approved
Compliance attestations present

Operational Readiness:

Monitoring and alerting configured for the release
Runbooks updated for new features
Rollback plan documented and tested

Present as a structured readiness report with GO/NO-GO recommendation.

Examples

"Show sprint velocity trends for the platform team" -- Analyze committed vs. completed points over the last N sprints
"How is our engineering investment split between features and bugs?" -- Calculate investment allocation with recommendations
"Help plan Sprint 24 based on our capacity" -- Calculate available capacity and recommend story point commitment
"Is the checkout-service v2.1 ready to release?" -- Run full readiness assessment with go/no-go recommendation
"Why are our sprints always over-committed?" -- Analyze estimation accuracy and scope change patterns

Performance Notes

Sprint analytics require consistent use of story points across the team -- mixed estimation methods reduce accuracy.
Investment allocation analysis needs accurate issue labeling -- unlabeled issues default to "unclassified" and skew results.
Capacity forecasts should account for context-switching overhead (typically 10-20% of engineering time).
Release readiness assessments should run at least 24 hours before the planned release date.

Troubleshooting

Velocity Data Inconsistent

Verify story points are assigned before sprint start (not mid-sprint)
Check that completed stories are marked done within the sprint, not after
Ensure the issue tracker integration is syncing correctly

Investment Allocation Missing Categories

Check issue labeling conventions -- all issues should have a type (feature, bug, tech debt)
Review the mapping between issue tracker labels and SEI categories
Add default categorization rules for unlabeled issues

Release Readiness Check Incomplete

Verify all pipeline stages have run for the release branch
Check that security scan results are available for the release artifacts
Ensure monitoring configuration has been validated in staging

Mehr aus diesem Repository

gleiches Repository

create-agent

harness/harness-skills

Create and update Harness AI agent instances - standalone templates for agentic workflows in pipelines. Use when asked to create agent, update agent, modify agent spec, build autonomous systems, or work with AI agents.

2026-07-0760

approve-exempt

harness/harness-skills

Approve pending Harness STO security exemptions (waivers) at their current scope or elevate them to Project, Org, or Account scope. Users say "approve" for both in-scope approval and higher-scope elevation — do not require the word "promote". Supports approving one exemption or a mixed list where each row has a different approval scope. Default workflow lists pending exemptions in chat (paginated preview) so the user picks by row number — no copying from the Harness UI. Use when a user wants to approve, sign off on, or clear pending exemptions, waive approvals, org-wide approval, or account-wide approval. Trigger phrases: approve exempt, approve exemption, approve waiver, sign off exemption, clear pending exemption, approve for org, approve for account, org-wide approval, account-wide approval, pending exemptions.

2026-06-1060

configure-agent-pr-attestation

harness/harness-skills

Use when asked to set up PR attestation, install harness-scs attestation hook, configure agent attestor, troubleshoot why agent attestation isn't uploading, or reconfigure an existing attestation hook (different SCM, new cosign key, updated Harness identity). Trigger phrases: set up PR attestation, install harness-scs attestation hook, configure agent attestor, why isn't my agent attestation uploading, set up agent attestation, configure PR signing, install attestation hook, configure claude attestation.

2026-06-0460

enforce-slsa

harness/harness-skills

Add an SLSA Verification (SlsaVerification) step to an existing Harness pipeline to verify SLSA provenance attestations and optionally enforce OPA policy sets on provenance data. Supports CI and CD (Deployment) including CI-only pipelines — append a Deploy stage via Phase 3b when verifying before deploy. Supports Docker, ECR, GCR, GAR, ACR, HAR, and Local artifacts. Only works with existing pipelines. Use when asked to verify SLSA, enforce SLSA policies, add SLSA verification step, validate SLSA attestation, or gate deploy on SLSA provenance. Trigger phrases: enforce SLSA, SLSA verification, verify SLSA, SLSA policy enforcement, SlsaVerification, verify SLSA attestation, add SLSA verify step.

2026-06-0360

generate-slsa

harness/harness-skills

Add a SLSA Generation step (YAML type: provenance) to an existing Harness pipeline to generate SLSA provenance and optionally attest with Cosign (keyless, key-based, or Vault). Supports container images (Docker, ECR, GCR, GAR, ACR, HAR) and Harness Local Stage artifacts. Place after image build/push; run sequentially after SBOM steps, not in parallel. Only works with existing pipelines. Use when asked to generate SLSA, add SLSA provenance, SLSA Generation step, attest SLSA, or configure SLSA Level 3 provenance in a pipeline. Trigger phrases: generate SLSA, SLSA generation, add SLSA step, SLSA provenance, attest SLSA, SlsaGeneration, provenance step, SLSA attestation, add provenance step.

2026-06-0360

create-sbom

harness/harness-skills

Add an SBOM (Software Bill of Materials) generation step to an existing Harness pipeline using Harness SCS SscaOrchestration (SBOM Orchestration). Supports container images and code repositories. Sources: docker, ECR, GCR, GAR, ACR, Harness AR (har), repository, and local workspace. Syft or cdxgen, SPDX or CycloneDX, optional SBOM attestation. Only works with existing pipelines. Use when asked to create an SBOM, generate a bill of materials, add SBOM to a pipeline, scan a container image or repo for components, or set up SBOM Orchestration. Trigger phrases: create SBOM, generate SBOM, add SBOM step, SBOM for image, SBOM for repo, scan for dependencies, SBOM Orchestration, add Generate SBOM step.

2026-06-0360