Run parity test c
Loop Engineering for AI coding agents, with real review boundaries. Your AI reviewer cannot edit code. Structurally.
npx -y skills add gustavo-meilus/superpipelines --skill run-parity-test-cAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when the user wants to run the parity-test-c pipeline on Tier 1c (Antigravity CLI) to analyze a text document and produce a structured markdown summary.
SKILL.md
5.6 KB, as published. Nobody here has run it
run-parity-test-c — Entry Skill
<overview> This skill initializes the pipeline run, surfaces Tier 1c degradation warnings, dispatches the analyzer and summarizer agents in sequence via the model_driven path of `sk-platform-dispatch`, and confirms the output file location on completion. </overview>Entry point for the
parity-test-cpipeline. Orchestrates the sequential dispatch ofanalyzerandsummarizeragents on Tier 1c (Antigravity CLI) via model_driven dispatch.
Platform Context
- Tier:
tier_1c(Antigravity CLI) - Dispatch mechanism:
model_driven— the host orchestrator drives subagent sequencing; noTask()primitive available. - model_field_format:
omit— agents do not declaremodel:ormodel_tier:in their dispatch prompts; the host owns model selection. - Degradation warning (MUST surface before execution):
"Antigravity uses dynamic subagents — per-step model assignment is not supported. Only the orchestrator's model tier is user-configurable. Subagent model selection is owned by Antigravity's orchestrator."
Workflow
<protocol>PHASE 0: PREFLIGHT
- Emit the Tier 1c degradation warning above.
- Resolve
{ROOT}viask-pipeline-paths(the scope root for tier_1c is the.agents/antigravitysubdirectory of the workspace root — resolved at runtime, never hardcoded). <!-- PORTABILITY_REWRITE: runtime resolution required --> - Resolve
{runId}= ISO-8601 timestamp (e.g.,20260526T143000Z). - Create temp directory:
{ROOT}/superpipelines/temp/parity-test-c/{runId}/. - Create
output/directory if absent:{ROOT}/output/. - Initialize
pipeline-state.jsonat{ROOT}/superpipelines/temp/parity-test-c/{runId}/pipeline-state.json:
{
"pipeline_id": "parity-test-c",
"run_id": "{runId}",
"started_at": "{iso8601}",
"plugin_version": "2.0.0",
"pattern": "1",
"status": "running",
"current_phase": 0,
"metadata": {
"source_tier": "tier_1c",
"runtime_tier": "tier_1c",
"orchestrator_tier": "medium",
"resolved_models": {}
},
"phases": [
{
"index": 0,
"step_id": "analyzer",
"name": "analyze",
"status": "pending",
"agent": "agents/superpipelines/parity-test-c/analyzer.md",
"outputs": [],
"error": null
},
{
"index": 1,
"step_id": "summarizer",
"name": "summarize",
"status": "pending",
"agent": "agents/superpipelines/parity-test-c/summarizer.md",
"outputs": [],
"error": null
}
]
}
- Ask the user to provide the path to the input text document if not already supplied. Record as
{INPUT_DOC}.
PHASE 1: DISPATCH ANALYZER (model_driven)
DISPATCH via model_driven orchestration:
Agent: analyzer
Protocol: {ROOT}/skills/superpipelines/parity-test-c/analyzer-protocol/SKILL.md
Context to pass:
- input_document_path: {INPUT_DOC}
- state_path: {ROOT}/superpipelines/temp/parity-test-c/{runId}/pipeline-state.json
- findings_output_path: {ROOT}/superpipelines/temp/parity-test-c/{runId}/analyzer-findings.json
- run_id: {runId}
- root: {ROOT}
Wait for terminal status from analyzer:
DONE→ updatepipeline-state.jsonphases[0].status = "completed"; advance to Phase 2.DONE_WITH_CONCERNS→ update phases[0].status = "completed_with_concerns"; emit concerns; advance to Phase 2.NEEDS_CONTEXT→ update phases[0].status = "blocked"; surface message to user; STOP.BLOCKED→ update phases[0].status = "blocked"; surface message to user; STOP.
PHASE 2: DISPATCH SUMMARIZER (model_driven)
DISPATCH via model_driven orchestration:
Agent: summarizer
Protocol: {ROOT}/skills/superpipelines/parity-test-c/summarizer-protocol/SKILL.md
Context to pass:
- findings_path: {ROOT}/superpipelines/temp/parity-test-c/{runId}/analyzer-findings.json
- output_path: {ROOT}/output/parity-test-c-summary.md
- state_path: {ROOT}/superpipelines/temp/parity-test-c/{runId}/pipeline-state.json
- run_id: {runId}
- root: {ROOT}
Wait for terminal status from summarizer:
DONE→ update phases[1].status = "completed"; advance to Phase 3.DONE_WITH_CONCERNS→ update phases[1].status = "completed_with_concerns"; emit concerns; advance to Phase 3.NEEDS_CONTEXT→ update phases[1].status = "blocked"; surface message to user; STOP.BLOCKED→ update phases[1].status = "blocked"; surface message to user; STOP.
PHASE 3: FINALIZE
- Update
pipeline-state.json:status:"completed"(or"completed_with_concerns"if any phase had concerns)completed_at: ISO-8601 timestamp
- Delete the temp run directory:
{ROOT}/superpipelines/temp/parity-test-c/{runId}/- On BLOCKED or NEEDS_CONTEXT: preserve the directory (do NOT delete); it holds resume state.
- Confirm to the user:
Pipeline
parity-test-ccompleted. Summary written to:{ROOT}/output/parity-test-c-summary.md