testpulse-v13-codex

Orchestrate contract-aware Codex changes for TestPulse v1.3 development.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/laceth/testpulse-proto --skill testpulse-v13-codex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testpulse-v13-codex
Source: https://github.com/laceth/testpulse-proto/tree/main/.github/skills/testpulse-v13-codex
Command: npx skills add https://github.com/laceth/testpulse-proto --skill testpulse-v13-codex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates contract-aware Codex changes for TestPulse v1.3 development.

Core Features & Use Cases

  • Contract-aware change orchestration across PRD-guided slices.
  • Cross-surface validation to keep backend, API, MCP, and frontend contracts aligned.
  • Focused testing: adds targeted tests and at least one failure-path scenario.
  • Progress tracking and guardrail alignment with PRD references.

Quick Start

Invoke this skill to start a v1.3 Codex slice with contract-aware validation and load the PRD and agent specs.

Frequently Asked Questions about testpulse-v13-codex

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep backend and frontend contracts aligned when making Codex changes?

Contract-aware Codex orchestration applies smallest contract-preserving edits across backend, API, and frontend surfaces, validating changes with targeted tests to keep TypeScript contracts aligned.

What's the best way to orchestrate PRD-guided development slices for TestPulse?

PRD-guided Codex orchestration loads Production PRD and agent specs to coordinate development slices, enforcing smallest contract-preserving edits and tracking progress with guardrail references.

How do I validate data-layer persistence and scheduler changes without breaking existing contracts?

Apply contract-aware validation by enforcing smallest contract-preserving edits and running targeted tests with at least one failure-path scenario across data-layer persistence, scheduler, and SSE components.

Can I use this orchestration approach for frontend resilience and prognosis feature development?

Yes, this orchestration applies across frontend resilience, prognosis, team scoping, and TypeScript contract sync, enforcing contract-preserving edits validated by targeted tests and guardrail references.

Why does my Codex task workflow need contract-aware validation for v1.3 development?

Contract-aware validation ensures smallest contract-preserving edits across data-layer, scheduler, and frontend surfaces, adding targeted tests and failure-path scenarios to prevent contract drift during development.

TestPulse v1.3 Codex orchestration not enforcing contract-preserving edits, what are the limitations?

Ensure the Production PRD and agent specs are loaded before invoking the slice, as guardrail alignment and cross-surface validation depend on these documents to enforce smallest contract-preserving edits.