Orchestrate seven autonomous steps from onboarding to final report.
npx skills add https://github.com/Fredasterehub/kiln --skill kiln-pipeline
Please help me install this Agent Skill. Skill: kiln-pipeline Source: https://github.com/Fredasterehub/kiln/tree/main/plugins/kiln/skills/kiln-pipeline Command: npx skills add https://github.com/Fredasterehub/kiln --skill kiln-pipeline
Kiln-pipeline solves the complexity of coordinating a seven-step software creation process by managing onboarding, brainstorming, research, architecture, build, validation, and final reporting across a team of specialized agents. It acts as the engine behind the /kiln-fire command, orchestrating autonomous steps, spawning agent rosters, and maintaining progress state through .kiln/STATE.md to enable resilient resumption.
Invoke /kiln-fire to start the seven-step pipeline orchestration.
High-intent search queries and answers about installing and using this skill.
Pipeline orchestration automates seven sequential software stages—onboarding, brainstorming, research, architecture, build, validate, and report—by spawning specialized agent teams. It manages state via STATE.md to coordinate progress and enable resilient resumption.
Automating onboarding through final reporting involves a seven-step pipeline that spawns specialized agents for brainstorming, research, architecture, build, and validation. It uses blueprint-based rosters and STATE.md to manage state and coordinate agent handoffs across milestones.
State management for resuming long-running pipelines relies on STATE.md to track milestone progress and coordinate agent rosters. This allows the orchestration engine to resume autonomous steps seamlessly after interruptions or failures.
Yes, autonomous agent orchestration requires jq and codex as dependencies. These tools support the pipeline's ability to spawn specialized teams, process state files, and coordinate the seven sequential stages from project onboarding to final report.
Yes, pipeline orchestration spawns and coordinates specialized agent teams—persistent minds, bosses, and workers—across seven stages. It manages handoffs from brainstorming through validation and reporting, ensuring disciplined collaboration and milestone tracking.
Pipeline orchestration resumes via STATE.md and blueprint-based rosters, so resumption fails if state files are corrupted or missing. Ensuring the .kiln directory and state tracking remain intact allows the engine to recover long-running pipelines seamlessly.
ricardorocheStandardize Pydantic tool schemas and agent state for multi-agent orchestration.
fcamacholMonitor registration process statuses and trigger change notifications.
numman-aliCoordinate multi-agent workflows by delegating tasks to specialized agents.
TeoSlayerDeploy a decentralized CI/CD pipeline across three agents with role-based coordination.
