Use this skill to plan a system of agents that handles software work from tickets to merged code. It defines shared terms for tasks, runs, and supporting services, and guides you in assigning products to each service slot and adding automation gradually.
Shared language for designing a software factory: the tasks it runs and the services it plugs into.
Run score Not tested
See how to installThis skill helps design a software factory: a system where agents handle work that starts from tickets, pull requests, or schedules. It gives you shared terms for the work itself (tasks), the events that start it (triggers), and each execution (runs). It also clarifies the roles of the ticket tracker, git host, orchestrator, runner, and optional observability platform.
For each task, you consider what it reads and writes, what it starts next, where a person reviews the result, and how duplicate runs are prevented. The design also accounts for automated checks and automated review, so you can expand automation in stages. Product choices can be mapped to each service role.
Use it when you want agents to triage tickets, review pull requests, or move software work through a defined process. It can also help compare service setups and decide where people need to check the work. If you have not chosen a starting point, the skill refers to task examples for common problems.
Product information needed for a design should be checked against the attached service surveys, followed by research into current options.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Nov 1, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Choose which related skill to use and in what order for planning, building, debugging, or maintaining software. It explains routes through the available workflows and helps select the next step based on your situation and project size.
Coordinate subagents, separate agents assigned tasks, to pursue a long-running goal in one session. Maintain dialogue with the user while improving working conditions, shared rules, and access to information needed for future tasks.
Summarize an ongoing conversation and launch a fresh background agent to continue the work. The handoff includes the next focus, references to existing documents, and suggested skills, with sensitive information removed.
Review code changes from a chosen Git reference against two separate criteria: documented coding standards and the original requirements. Independent reviewers check each criterion, then present findings separately so convention problems and requirement gaps remain visible.
Design modules that offer substantial behavior through a small interface, the rules callers must understand. Use shared design terms to simplify usage, contain complexity, choose where implementations can vary, and make behavior easier to test.
Investigate difficult bugs and performance slowdowns by building a repeatable test or script that detects the exact symptom. Reduce the failing case, compare possible causes, and verify the fix with checks that catch the bug if it returns.