skills.rest
YurainSoon
YurainSoonCOMMUNITY
Explore all skills by this author →
GitHub

phase2-implementation

Orchestrate Phase 2 implementation cycles with fidelity checks and round caps.

Updated Apr 19, 2026
Search Tags:#orchestrate#fidelity#coder#phase-2#fidelity-checker#module-iteration
One-click install
npx skills add https://github.com/YurainSoon/research-director --skill phase2-implementation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: phase2-implementation
Source: https://github.com/YurainSoon/research-director/tree/main/.claude/skills/phase2-implementation
Command: npx skills add https://github.com/YurainSoon/research-director --skill phase2-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase 2 orchestration of the Phase 2 implementation pipeline, coordinating the Coder and Fidelity Checker to deliver modular, converged code across all modules.

Core Features & Use Cases

  • End-to-end orchestration of the Phase 2 loop: precondition verification, module enumeration, per-module coding and fidelity checks, convergence tracking, and escalation when needed.
  • Per-module round management with a hard cap of 3 fidelity rounds to ensure timely progress and clear handoffs to Phase 3.
  • Cross-module integrity checks and artifact generation: fidelity reports, per-module READMEs, and status summaries to support downstream experiment planning.

Quick Start

Begin Phase 2 orchestration from the confirmed Phase 1 design and begin iterating the first module.

Frequently Asked Questions about phase2-implementation

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

FAQPage Schema
How do I orchestrate phase 2 implementation across multiple modules?▼

To orchestrate phase 2 implementation, you coordinate the confirmed spec modules by guiding the Coder and Fidelity Checker through per-module cycles. It verifies preconditions, enumerates modules, and tracks convergence using a Step 1–7 workflow.

What is the maximum number of fidelity rounds allowed per module during implementation?▼

The maximum number of fidelity rounds allowed per module is 3. This hard cap ensures timely progress and enforces clear escalation or handoffs to Phase 3 when convergence is not achieved.

How do I track convergence and manage module iteration during code implementation?▼

You track convergence and manage module iteration by generating fidelity reports and tracking per-module rounds. The workflow detects convergence within each cycle and escalates when modules fail to pass checks after the defined round limits.

When do I need to use a fidelity checker for modular code generation?▼

You need a fidelity checker for modular code generation when applying a validated method design handoff. It enforces preconditions, verifies cross-module integrity, and records outcomes to support downstream experiment planning.

What artifacts are generated when coordinating end-to-end implementation workflows?▼

Artifacts generated when coordinating end-to-end implementation workflows include fidelity reports, per-module READMEs, and status summaries. These outputs document the convergence tracking and support downstream Phase 3 experiment planning.

Related Skills

Explore More Software Engineering Skills→
YurainSoonYurainSoon

phase1-method-design

Orchestrate the Architect-Confirmer loop until Phase 1 converges.

Community
Advanced
jineynejineyne

speckit-plan

Generate implementation plans and design artifacts from spec-kit repositories.

Community
Advanced
babywormbabyworm
43

rtl-p5s-perf-verify

Measure RTL throughput, latency, and stall cycles against BFM baselines.

Community
Advanced
macaughmacaugh
5

Static Vulnerability Analysis

Detects injection, memory safety and authorization flaws in multiple languages.

Community
Advanced