Dirtytrii GStack Spec Adapter
This is a Codex role-system adapter for Garry Tan's gstack gstack-spec method.
When To Use
Use this when:
- the user has intent but no implementation-ready shape;
- a downstream developer prompt needs a clearer spec;
- acceptance criteria or non-goals are missing;
- the user explicitly invokes
$gstack-spec.
Workflow
- Keep the active role boundary. Do not expand scope just because this gstack method is useful.
- Read the relevant repo/docs/evidence first when the task depends on current state.
- Read
../gstack/references/methodology.mdif you need the shared method map, then use the section namedArchitecture And Product Methods. - Produce: a concise executable spec with goals, non-goals, scope, acceptance criteria, risks, and open questions.
- Return the result in the active role's normal format, including boundaries, validation, and unresolved decisions when applicable.
Boundaries
- Treat upstream gstack as external methodology, not local-owned project state.
- Do not run upstream gstack runtime, telemetry, browser-cookie import, upgrade checks, or host routing injection automatically.
- Do not create or edit
CLAUDE.md,.claude/,.agents/, or upstream routing files unless the user explicitly asks for upstream gstack installation work. - Do not write files, commit, push, deploy, restart, migrate, clean, delete, or change production unless the active role prompt explicitly allows it.
- Preserve this repository's
QAversus测试split: formal test cases/reports belong to测试and$test-case-report-builder.