full-cycle

Chain seven ProductionOS workflows from audit through shipping into a complete lifecycle.

8|Updated Mar 17, 2026

Search Tags:#automation #workflow #end-to-end #code-quality #production-os #audit-upgrade-research-plan

Ready to run

npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill full-cycle-shaheerkhawaja

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: full-cycle
Source: https://github.com/ShaheerKhawaja/ProductionOS/tree/main/skills/full-cycle
Command: npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill full-cycle-shaheerkhawaja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Chains seven ProductionOS workflows into a complete lifecycle to deliver production-ready code.

Core Features & Use Cases

Orchestrates an end-to-end production cycle by layering audit, upgrade, deep research, CEO plan, auto-swarm fixes, self-evaluation, and ship.
Produces structured phase outputs and traceable artifacts in .productionos for review and governance.
Scales to large codebases and pre-launch readiness with configurable depth and parallelism.

Quick Start

Invoke the full-cycle skill to run audit-upgrade-research-plan-swarm-fix-eval-ship on your codebase.

Frequently Asked Questions about full-cycle

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

FAQPage Schema

How do I orchestrate an end-to-end production cycle for a large codebase?▼

To orchestrate an end-to-end production cycle for a large codebase, you can chain multiple workflows covering audit, upgrade, research, planning, automated fixes, evaluation, and shipping. This delivers production-ready code by executing a multi-phase process with configurable depth and parallelism.

What does a full production lifecycle workflow include for pre-launch readiness?▼

A full production lifecycle workflow for pre-launch readiness includes seven phases: audit, upgrade, deep research, CEO plan, auto-swarm fixes, self-evaluation, and shipping. Each phase generates structured outputs and traceable artifacts written to .productionos files for governance and review.

Can I automate code quality fixes and planning for major project milestones?▼

Yes, you can automate code quality fixes and planning for major milestones by running an auto-swarm fix phase followed by a self-evaluation phase. This enforces a structured review process that scales to large codebases and ensures production-ready code before shipping.

How do I configure the depth of an automated code audit and upgrade process?▼

You can configure the depth of an automated code audit and upgrade process when initiating the lifecycle. This configurable depth allows the multi-phase workflow to scale appropriately for large codebases and pre-launch readiness requirements.

Does the production cycle workflow require external dependencies to run?▼

No, the production cycle workflow requires no external dependencies to run. It operates independently to chain the audit, upgrade, research, planning, swarm-fix, evaluation, and shipping phases into a complete lifecycle for delivering production-ready code.

Where are phase outputs stored during an end-to-end code review and fix cycle?▼

Phase outputs are stored as structured, traceable artifacts in .productionos files during the end-to-end code review and fix cycle. This ensures that every audit, research, and planning phase result is documented for governance and review.