Programming Agent Pack Selector
Use this skill for Programming work focused on select only needed programming specialists: backend, frontend, DB, security, QA, DevOps, mobile, or architecture.
Workflow
- Restate the user outcome, target quality level, constraints, and definition of done.
- Inspect the current project before proposing code, design, sources, or dependencies.
- Use Srednoff OS mode/domain routing; if TURBO is active, compare top sources and run deeper critique.
- Prefer existing project conventions and proven sources over generic invention.
- Validate with the narrowest checks that prove the result, expanding validation for high-risk or TURBO work.
- Report facts, commands, source decisions, remaining risks, and exact next steps.
Checklist
- Facts separated from assumptions.
- Source/provenance reviewed when external code, components, assets, or advice are used.
- Security, privacy, accessibility, performance, and rollback considered when relevant.
- Token cost justified by concrete quality gain unless TURBO is explicitly active.
- No broad context loading when a deterministic script or narrow reference is enough.
Guardrails
- Do not perform destructive, paid, production, publishing, account-changing, trading, legal, financial, or externally visible actions without explicit confirmation.
- Do not expose secrets, tokens, cookies, private keys, personal data, or confidential business data.
- Do not copy third-party code or assets without license/provenance review.
- If validation is impossible, state why and provide a concrete manual verification path.
1---2name: programming-agent-pack-selector3description: Use for complex programming work when Codex should choose a narrow set of specialist agents without bloating context.4---5
6# Programming Agent Pack Selector
7
8Use this skill for Programming work focused on select only needed programming specialists: backend, frontend, DB, security, QA, DevOps, mobile, or architecture.
9
10## Workflow
11
121. Restate the user outcome, target quality level, constraints, and definition of done.
132. Inspect the current project before proposing code, design, sources, or dependencies.
143. Use Srednoff OS mode/domain routing; if TURBO is active, compare top sources and run deeper critique.
154. Prefer existing project conventions and proven sources over generic invention.
165. Validate with the narrowest checks that prove the result, expanding validation for high-risk or TURBO work.
176. Report facts, commands, source decisions, remaining risks, and exact next steps.
18
19## Checklist
20
21- Facts separated from assumptions.
22- Source/provenance reviewed when external code, components, assets, or advice are used.
23- Security, privacy, accessibility, performance, and rollback considered when relevant.
24- Token cost justified by concrete quality gain unless TURBO is explicitly active.
25- No broad context loading when a deterministic script or narrow reference is enough.
26
27## Guardrails
28
29- Do not perform destructive, paid, production, publishing, account-changing, trading, legal, financial, or externally visible actions without explicit confirmation.
30- Do not expose secrets, tokens, cookies, private keys, personal data, or confidential business data.
31- Do not copy third-party code or assets without license/provenance review.
32- If validation is impossible, state why and provide a concrete manual verification path.
srednoff888-art