mphaxise/gstack-port-for-codex - Page 3

strategic-reading

Read a source through the lens of a specific strategic problem and turn it into an applied playbook.

capture

Save a thought, note, or short artifact into the local brain substrate with citations and a clear receipt.

context-save

Save working context, git state, decisions, and remaining work so a future Codex session can resume cleanly.

document-generate

Generate or refresh missing project documentation using a Diataxis-style split of tutorials, how-to guides, reference, and explanation.

schema-author

Evolve the local brain schema or page-type conventions when the current taxonomy cannot describe the material cleanly.

benchmark

Performance baseline and regression workflow for Codex. Use when load time, resource size, or user-facing performance should be measured and compared over time.

canary

Post-deploy monitoring workflow for Codex. Use when a live deployment should be watched for obvious breakage, regressions, or unhealthy signals.

codex

Independent second-opinion workflow for Codex. Use when the user wants an adversarial review, a second-pass challenge, or a separate consultation mode inside the current workflow.

cso

Security audit workflow for Codex. Use when a repo, feature, or system should be reviewed for concrete security risks before or after shipping.

devex-review

Live developer-experience audit for Codex. Use when docs, setup, onboarding, CLI, API, or SDK workflows should be tested as a real user would experience them.

document-release

Post-ship documentation sync for Codex. Use when shipped changes should be reflected in README, architecture docs, contributor docs, or release notes.

freeze

Edit-scope boundary for Codex. Use when changes should be restricted to one directory or subsystem during a task.

guard

Maximum-safety workflow for Codex. Use when the task needs both destructive-action caution and a strict edit boundary.

health

Codebase health-check workflow for Codex. Use when the repo should be scored or summarized across tests, linting, type checks, and structural quality signals.

land-and-deploy

Merge-and-verify release workflow for Codex. Use when a reviewed change should be landed, deployed, and checked in production.

learn

Project-learning management for Codex. Use when the user wants to capture, review, prune, or export recurring patterns, preferences, and pitfalls across sessions.

plan-design-review

Pre-implementation design review for Codex. Use when a plan has user-facing UI or UX and should be critiqued before implementation starts.

plan-devex-review

Pre-implementation developer-experience review for Codex. Use when a plan is for APIs, CLIs, SDKs, docs, or developer-facing platforms.

plan-tune

Planning-preference tuning workflow for Codex. Use when recurring plan questions, scope choices, or explanation style should be captured and reused across future planning work.

setup-deploy

Deployment setup workflow for Codex. Use when a repo needs its deployment path, production URL, health checks, or release verification steps documented before automated deploy work.

unfreeze

Clear a prior edit boundary in Codex. Use when a frozen scope should be widened and broader edits are now allowed.

investigate

Root-cause-first debugging for Codex. Use when the user reports a bug, unexpected behavior, or an error and wants investigation before speculative fixes.

office-hours

YC-style product and project framing for Codex. Use when the user has a new idea, wants to brainstorm whether something is worth building, or needs sharper framing before plan review.

plan-ceo-review

Founder-style plan review for Codex. Use when a user wants to pressure-test a product or feature plan before implementation.

daily-task-manager

GBrain-inspired task lifecycle management for Codex. Use when the user wants to add, complete, defer, remove, or review tasks in a durable tracker.

daily-task-prep

GBrain-inspired morning prep for Codex. Use when the user wants a working view of today's meetings, open threads, and top tasks.

data-research

GBrain-inspired structured research for Codex. Use when the user wants tracked extraction, recurring data collection, or a canonical tracker built from files, connectors, or web sources.

publish

GBrain-inspired publishing workflow for Codex. Use when a memo, report, or saved artifact should become a clean shareable file.

repo-architecture

GBrain-inspired filing rules for this Codex package. Use when deciding where new skills, docs, registries, scripts, or tests should live in the repo.

reports

GBrain-inspired report persistence for Codex. Use when the user wants a saved report, a latest-report lookup, or stable report categories over time.

skill-creator

GBrain-inspired skill authoring for Codex. Use when creating or extending a skill in this repo while keeping the package coherent.

soul-audit

GBrain-inspired identity and cadence setup for Codex. Use when defining the package's identity files, access posture, user context, or operational cadence.

webhook-transforms

GBrain-inspired event transforms for Codex. Use when a JSON event payload should be replayed into the local brain as a meeting or source artifact.

plan-eng-review

Engineering-manager style plan review for Codex. Use when the product direction is chosen and the user needs architecture, test, and execution rigor before coding.

retro

Team-aware engineering retrospective for Codex. Use when the user wants a weekly or windowed retrospective based on git history.

review

Pre-landing PR review for Codex. Use when the user asks for a code review or wants structural issues found before a branch lands.

ship

Release workflow for Codex. Use when a feature branch is ready to be tested, reviewed, pushed, and opened as a PR.