implementation_flow

Implements approved design changes and executes unit tests with traceable evidence for QA handoff.

4|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/synthaicode/XRefKit --skill implementation-flow-synthaicode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementation_flow
Source: https://github.com/synthaicode/XRefKit/tree/main/skills/implementation_flow
Command: npx skills add https://github.com/synthaicode/XRefKit --skill implementation-flow-synthaicode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns approved software designs into implemented code and unit test results without letting the AI guess missing design intent, hide unresolved items, or close quality findings it does not own. ## Core Features & Use Cases - Scoped Implementation: Executes the manufacturing sequence CAP-MFG-001 (implementation) and CAP-MFG-002 (unit test execution) only against traced, approved change targets. - Assumption Gap Handling: Classifies implementation gaps as clarification_needed, evidence_missing, scope_conflict, local_choice_allowed, or basis_refuted, and escalates tradeoffs instead of deciding locally. - Quality Feedback Returns: Fixes concrete in-scope findings with evidence, escalates conflicts, and hands dispositions back to the quality source without closing its findings. - Use Case: Given an approved design, test plan, and coding rules for a C# change, run this Skill to produce the code diff, unit test evidence, unresolved lists, and a QA-ready handoff package. ## Quick Start Ask the AI to run the implementation_flow Skill through xrefkit to implement the approved design changes and execute the planned unit tests for the named target files.

Frequently Asked Questions about implementation_flow

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

FAQPage Schema
How do I implement an approved design change with traceable evidence?▼

Run this Skill through xrefkit with the approved design, test plan, target files, and coding rules. It executes implementation then unit tests, recording which design artifact each change realizes and which test design item each test covers.

How should AI handle quality feedback during code implementation?▼

Classify each finding as implementation_local, tradeoff_or_scope_conflict, requires_design_or_requirement_decision, or requires_specialist_or_dependency_decision. Fix concrete in-scope items with evidence and escalate anything involving tradeoffs or decisions outside implementation authority.

What happens when the design leaves structural behavior undefined?▼

The Skill stops implementation planning and routes through constraint-derivation Skills before coding. It never guesses behavior from DDL, UI, state transitions, integrations, batch rules, or auth rules.

Can this Skill close quality review findings itself?▼

No. It hands back finding ids, dispositions, fix evidence, and verification evidence to the quality source, which must re-run or re-dispose its own check. Implementation context never closes the source finding.

When should implementation_flow not be used?▼

Do not use it to discover new design intent, resolve business, security, release, dependency, or license decisions locally, or replace QA review. It only realizes already-approved, bounded differences.