parallax-core

スター0

フォーク0

更新日2026年7月18日 14:52

Evidence-first coding protocol for ambiguous, multi-file, high-risk, or quality-sensitive engineering. Use when state ownership, blast radius, timing, verification, or recovery materially affects correctness.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

Master0fFate

Master0fFate/parallax-piagent

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Parallax Core

Use the parallax tool to record protocol progress. Do not perform check-ins as ceremony; investigate first and attach concrete evidence.

Ambiguity: Rate LOW, MEDIUM, or HIGH. Ask only questions whose answers materially change implementation. Record assumptions when safe defaults exist.
Invariants: Identify the exact state owner and truth source; feedback/error surface; deletion/import blast radius; and timing, ordering, cancellation, or race constraints.
Gate: Define observable acceptance checks, existing pattern evidence, security boundaries, and rollback or recovery.
Execute: Make the smallest coherent change. Parallax batches sibling file mutations and verifies once at turn end.
Commit: Choose full solution, pragmatic partial with explicit deferrals, or hold due to a named blocker.
Summary: State what changed, evidence from checks, edge cases covered, and remaining risk.

For trivial work, keep each step short. For complex plans, switch to PLAN mode and use parallax_hyperplan; for post-build review, switch to DEBUG mode.

このリポジトリの他の Skills

同じリポジトリ

parallax-debug

Master0fFate/parallax-piagent

Run an evidence-based post-build review for correctness, regressions, security, performance, and maintainability. Use after implementation or when asked to debug, audit, harden, or verify production readiness.

2026-07-180

parallax-horizon

Master0fFate/parallax-piagent

Execute substantial multi-stage work through durable project-local plans, research, decisions, checkpoints, retries, and final audit. Use for long-running tasks that must survive compaction or session resume.

2026-07-180

parallax-plan

Master0fFate/parallax-piagent

Create grounded, execution-ready engineering plans without mutating files. Use for migrations, architecture changes, multi-file features, unclear requirements, or when the user asks to plan before implementation.

2026-07-180

name	parallax-core
description	Evidence-first coding protocol for ambiguous, multi-file, high-risk, or quality-sensitive engineering. Use when state ownership, blast radius, timing, verification, or recovery materially affects correctness.
license	MIT

Parallax Core

Use the parallax tool to record protocol progress. Do not perform check-ins as ceremony; investigate first and attach concrete evidence.

Ambiguity: Rate LOW, MEDIUM, or HIGH. Ask only questions whose answers materially change implementation. Record assumptions when safe defaults exist.
Invariants: Identify the exact state owner and truth source; feedback/error surface; deletion/import blast radius; and timing, ordering, cancellation, or race constraints.
Gate: Define observable acceptance checks, existing pattern evidence, security boundaries, and rollback or recovery.
Execute: Make the smallest coherent change. Parallax batches sibling file mutations and verifies once at turn end.
Commit: Choose full solution, pragmatic partial with explicit deferrals, or hold due to a named blocker.
Summary: State what changed, evidence from checks, edge cases covered, and remaining risk.

For trivial work, keep each step short. For complex plans, switch to PLAN mode and use parallax_hyperplan; for post-build review, switch to DEBUG mode.