Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

harness-spec

Étoiles23

Forks2

Mis à jour27 mai 2026 à 12:12

Draft or refine harness artifact contracts under .pi/harness/specs. Use when defining PlanPacket, RunTrace, HarnessRunRecord, eval verdicts, or PostHog event schemas for ultimate-pi.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

aryaniyaps

aryaniyaps/ultimate-pi

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	harness-spec
description	Draft or refine harness artifact contracts under .pi/harness/specs. Use when defining PlanPacket, RunTrace, HarnessRunRecord, eval verdicts, or PostHog event schemas for ultimate-pi.

harness-spec

When to use

Adding or bumping harness JSON schemas
Aligning extensions with contract versions
Documenting breaking vs compatible schema changes

Workflow

Read .pi/harness/specs/README.md for versioning rules (contract_version, optional fields only for compatible changes).
Edit or add schema under .pi/harness/specs/.
Update affected extensions to emit matching custom entries.
Run node "$UP_PKG/.pi/scripts/harness-verify.mjs" (see .pi/scripts/README.md).
Add or update a formal decision record in the target project's standard decision-log location for breaking changes.

Rules

Never use lean-ctx in harness paths; use normal Read/Grep or context-mode via harness-context.
Keep @posthog/pi unchanged; harness events belong in harness-posthog-event.schema.json.

Plus depuis ce dépôt

même dépôt

harness-git-commit

aryaniyaps/ultimate-pi

Commit staged git changes with configurable message format and Co-authored-by trailer from .pi/auto-commit.json. Use when the user asks to commit, when /harness-auto or harness run completion requires a commit, or before any git commit — never use raw git commit -m.

2026-06-0723

harness-context

aryaniyaps/ultimate-pi

Compile task-specific harness context using context-mode and graphify. Use for architecture questions, large codebase context before harness-plan or harness-run. NEVER use lean-ctx on harness paths.

2026-05-2723

harness-debate-plan

aryaniyaps/ultimate-pi

Plan-phase Review Gate debate — pi-messenger threads, lane YAML, bus tools for parent orchestrator.

2026-05-2723

harness-decisions

aryaniyaps/ultimate-pi

Structured user decisions via ask_user for harness setup, planning, and governance forks. Use with /harness-setup, /harness-plan, harness-auto plan phase, and when agents emit human_required.

2026-05-2723

harness-eval

aryaniyaps/ultimate-pi

Deprecated — use harness-review skill and /harness-review for the full post-run gate. This file remains as a pointer for older prompts.

2026-05-2723

harness-governor

aryaniyaps/ultimate-pi

Enforce harness governance phases, policy gates, budgets, and promotion rules. Use during execute, evaluate, merge, or when interpreting policy-gate / budget-guard messages.

2026-05-2723

name	harness-spec
description	Draft or refine harness artifact contracts under .pi/harness/specs. Use when defining PlanPacket, RunTrace, HarnessRunRecord, eval verdicts, or PostHog event schemas for ultimate-pi.

harness-spec

When to use

Adding or bumping harness JSON schemas
Aligning extensions with contract versions
Documenting breaking vs compatible schema changes

Workflow

Read .pi/harness/specs/README.md for versioning rules (contract_version, optional fields only for compatible changes).
Edit or add schema under .pi/harness/specs/.
Update affected extensions to emit matching custom entries.
Run node "$UP_PKG/.pi/scripts/harness-verify.mjs" (see .pi/scripts/README.md).
Add or update a formal decision record in the target project's standard decision-log location for breaking changes.

Rules

Never use lean-ctx in harness paths; use normal Read/Grep or context-mode via harness-context.
Keep @posthog/pi unchanged; harness events belong in harness-posthog-event.schema.json.