Nist Test
Walk NIST SSDF Phase 4 (Test) and file GitHub epics for the two test practices — PW.7 reviewing and analyzing human-readable code (peer review and SAST), PW.8 testing executable code (dynamic analysis, fuzzing, penetration testing). Use when setting up or auditing a test pipeline, deciding what security testing a repo needs, wiring SAST or DAST into CI, or when the user mentions NIST SSDF, SP 800…
Github Project Board
Use when Codex needs to inspect or update GitHub Projects v2 boards for CloudPeek issues or pull requests: finding project membership, adding items to the correct board, moving cards through Status/phase values, claiming work, moving bug fixes through Open/Claimed/Release Candidate/Closed/Stale, or verifying project-board state after issue or PR work.
Nist Plan
Walk NIST SSDF Phase 1 (Plan & Requirements) and file GitHub epics for the five "Prepare the Organization" practices — PO.1 security requirements, PO.2 roles and responsibilities, PO.3 supporting toolchains, PO.4 criteria for security checks, PO.5 secure development environments. Use when starting a new product or a major feature planning cycle, when setting up secure-SDLC governance for a repo,…
Nist Release
Walk NIST SSDF Phase 5 (Release) and file GitHub epics for the three release practices — PS.2 verifying software release integrity (signing, checksums, provenance), PS.3 archiving each release and producing an SBOM, PW.9 shipping secure settings by default. Use when preparing or auditing a release process, adding artifact signing or SBOM generation, reviewing default configuration for insecure de…
Nist Design
Walk NIST SSDF Phase 2 (Design) and file GitHub epics for the three design practices — PW.1 threat modeling and secure-by-design, PW.2 independent design review, PW.4 reuse of well-secured components instead of duplicating functionality. Use before starting a new major feature, when threat modeling an architecture, when reviewing a design for security compliance, or when the user mentions NIST SS…
Nist Build
Walk NIST SSDF Phase 3 (Build) and file GitHub epics for the three build practices — PS.1 protecting code from unauthorized access and tampering, PW.5 secure coding practices, PW.6 hardening the compiler, interpreter, and build toolchain. Use when setting up or auditing a build pipeline, hardening CI, reviewing branch protection and commit signing, or when the user mentions NIST SSDF, SP 800-218,…
Implement Issue
Use when the user wants to implement a GitHub issue end-to-end: fetch issue context, claim it (assign yourself, set status to In progress), create a branch, plan, code, validate, push, and open a draft PR.
Pr From Branch
Use when the user wants to draft a GitHub pull request title and body from the current branch, choose existing repo labels, and open the PR with gh after confirmation.
Plan To Issue
Use when the user wants to turn the just-approved plan from the current conversation into a self-contained GitHub issue that another agent can implement cold.
Prettify
Use when the user wants to turn a message, document, or provided text into a polished, self-contained visual HTML infographic saved to a local file.
Feature Development Workflow
Deliver a GitHub issue from pickup to PR handoff. Use when you are asked to pick up, plan, implement, test, review, push, or open/update a PR for a feature, adapter, worker lane, runtime change, results/persistence change, approval/HITL progression, observability work, or a stacked change against an existing branch.
Nist Respond
Walk NIST SSDF Phase 6 (Operate & Respond) and file GitHub epics for the three "Respond to Vulnerabilities" practices — RV.1 identifying and confirming vulnerabilities on an ongoing basis, RV.2 assessing, prioritizing, and remediating them, RV.3 root-cause analysis so a class of bug stops recurring. Use when standing up vulnerability management, writing a disclosure policy or SECURITY.md, setting…
Release Candidate Review
Compare one or more release-candidate PRs against their design PR, produce a section-by-section pick-and-mix report (which RC implemented each part of the design best), identify design flaws needing amendment, and open a PR with the report on top of the design branch. Use when the user asks to review/compare RCs against a design, pick the best parts of competing implementations, or judge which RC…
Gh Release Train Merge
Use when Codex needs to create or maintain a GitHub release/integration branch and draft PR by merging multiple existing PRs into it one at a time, especially when the user requires the original PRs to be commented on, retargeted if needed, merged through GitHub, and recorded as MERGED rather than merely having their commits manually merged into another branch.