conductor-feature-prepare

Name: conductor-feature-prepare
Availability: InStock
Author: rashidee

Orchestrate multi-version generation of module models, HTML mockups, specifications, and tests.

3|Updated Mar 15, 2026

Search Tags:#automation #devops #versioning #orchestrate #artifact-generation #ralph-loop #context-artifacts

Ready to run

npx skills add https://github.com/rashidee/co2-skills --skill conductor-feature-prepare

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conductor-feature-prepare
Source: https://github.com/rashidee/co2-skills/tree/main/skills/conductor-feature-prepare
Command: npx skills add https://github.com/rashidee/co2-skills --skill conductor-feature-prepare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Context artifacts preparation orchestrator — coordinates generation of module models, HTML mockups, technical specifications, and test specifications for a given application, supporting optional version filtering and module scoping.

Core Features & Use Cases

Orchestrates multi-version artifact generation for an application, with optional version and module filters.
Tags untagged user stories in PRD.md to ensure stable IDs across artifacts.
Generates and updates module models, HTML mockups, technical specifications, and test specifications via sub-skills.
Supports resuming and safe re-run via Ralph Loop integration and idempotent execution.

Quick Start

Trigger Ralph Loop and begin Phase 0 to start artifact preparation for an application.

Frequently Asked Questions about conductor-feature-prepare

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

FAQPage Schema

How do I automate context artifact generation across multiple application versions?▼

You can automate context artifact generation by orchestrating sub-skills to resolve versions, tag user stories, and produce module models, HTML mockups, specifications, and tests with strict version sequencing and mandatory Ralph Loop activation.

What is the best way to keep user story IDs stable across generated technical specifications and test artifacts?▼

Tag untagged user stories in PRD.md to ensure stable IDs across all generated artifacts, coordinating updates to module models, HTML mockups, specifications, and tests consistently across versions.

Can I resume artifact generation safely if an orchestration loop iteration fails halfway through?▼

Resume artifact generation safely via Ralph Loop integration and idempotent execution, which allows safe re-runs and continuation from the last successful state without duplicating previously generated outputs.

Does this orchestration approach support filtering artifact generation by specific modules and version sets?▼

Artifact generation supports optional version filtering and module scoping, allowing you to target specific application versions and modules while maintaining strict version sequencing and auditable outputs.

Why does artifact orchestration require mandatory Ralph Loop activation instead of running a single pass?▼

Mandatory Ralph Loop activation enforces idempotent execution and resumable iterations, ensuring complete, auditable artifact generation across versions rather than risking incomplete outputs from a single pass.

When should I not use an orchestrated approach for generating module models and HTML mockups?▼

Avoid orchestrated multi-version artifact generation for simple, single-version tasks without strict sequencing needs, as the mandatory Ralph Loop and sub-skill coordination add overhead suited for complex, multi-version application contexts.