skills.rest
GrinRus
GrinRusCOMMUNITY
Explore all skills by this author →
GitHub

implement

Run the implement stage loop and emit a canonical stage result JSON.

5|Updated Oct 9, 2025
Search Tags:#implement#workflow-orchestration#aidd#stage-result#stage-loop#ticket-scope
One-click install
npx skills add https://github.com/GrinRus/ai_driven_dev --skill implement-grinrus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/GrinRus/ai_driven_dev/tree/main/skills/implement
Command: npx skills add https://github.com/GrinRus/ai_driven_dev --skill implement-grinrus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executes the implement-stage loop to process the next scoped work item by coordinating the stage-chain orchestration and artifact handling, ensuring smooth handoffs between preflight, runtime, and postflight.

Core Features & Use Cases

  • Stage-loop orchestration for the implement stage, including canonical stage-runtime paths and artifact generation.
  • Reads and writes required by the stage contract (actions, context, and stage results) to keep the loop aligned with PRD-like workflows.
  • Use Case: When a work item enters the implement loop, this skill enforces the sequence of preflight -> stage-runtime -> actions_apply -> stage-result, and produces the canonical stage result for downstream steps.

Quick Start

Resolve the active ticket and scope, ensure loop artifacts are present, and run the implement runtime to begin the loop.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I orchestrate an implement stage loop for a new scoped work item?▼

To orchestrate an implement stage loop, the skill coordinates the preflight, stage-runtime, actions_apply, and stage-result sequence. It processes the next scoped work item by validating inputs and ensuring smooth handoffs between preflight, runtime, and postflight.

What is the canonical stage result format for workflow orchestration?▼

The canonical stage result is a JSON file emitted at aidd/reports/loops/<ticket>/<scope_key>/stage.implement.result.json. This artifact format ensures downstream stage-chain steps can reliably consume the implement stage's output.

How do I ensure stage-chain consistency across ticket scope in an implement loop?▼

You ensure stage-chain consistency by running the implement runtime to enforce the canonical stage-runtime path and artifact generation. This handles required reads and writes to keep the loop aligned with PRD-like workflows.

Do I need specific loop artifacts before starting the implement stage runtime?▼

Yes, you need to resolve the active ticket and scope, and ensure all required loop artifacts are present before running the implement runtime. This satisfies the runtime contract by validating inputs and using provided entrypoints.

Why does my workflow orchestration fail to generate the stage result during the implement loop?▼

Workflow orchestration may fail to generate the stage result if the preflight validation fails or if loop artifacts for the ticket scope are missing. The skill requires valid inputs and provided entrypoints to successfully emit the canonical stage result.

Related Skills

Explore More Software Engineering Skills→
GrinRusGrinRus
5

idea-new

Initialize a new feature ticket by deriving a slug and generating PRD scaffolding.

Community
Advanced
Eric-NessEric-Ness

create-meta-prompts

Create XML-structured metadata prompts for Claude-to-Claude multi-stage workflows.

Community
Advanced
JDL440JDL440

Editor-Aligned Writer Preflight

Apply a preflight checklist before drafting to align Writer output with Editor expectations.

Community
Intermediate
GrinRusGrinRus
5

qa

Automate QA validation, reporting, and stage-flow governance for development cycles.

Community
Advanced