Menü
synthetic test fixture for migration 0009 — after-idempotent
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | agentic-apps-workflow |
| version | 1.8.0 |
| description | synthetic test fixture for migration 0009 — after-idempotent |
Bootstrap a fresh project with the AgenticApps Superpowers + GSD + gstack workflow by installing the LATEST snapshot directly — no migration replay. Lays down the current end-state project artifacts (the workflow skill, CLAUDE.md sections, hooks, settings, planning config, version stamp) in one shot. Use when the user runs "/setup-agenticapps-workflow", "set up the workflow", "install agenticapps workflow", or "scaffold this project". Idempotent — refuses to re-run on a project that already has `.claude/skills/agentic-apps-workflow/` and routes to `/update-agenticapps-workflow` instead. Fail-closed on an unverified snapshot: refuses to install until the drift guard (`check-snapshot-parity.sh`) passes, so a raw/stale seed can never be laid down silently.
Enforces the spec-first development workflow using Superpowers + GSD + gstack for any AgenticApps project. This skill MUST activate whenever Claude is asked to implement, build, code, fix, refactor, or design anything in the current project — regardless of whether the user explicitly mentions the workflow. Triggers on: "let's work on [issue]", "implement the [feature]", "build the [component]", "fix the [bug]", any task involving writing or changing code, creating architecture, or making technical decisions. The skill ensures every piece of work follows the Superpowers + GSD + gstack discipline and produces traceable decision artefacts. Use this even when the user just says "start working" or references a Linear issue number.
Declare-first TypeScript discipline for new modules in TS-primary AgenticApps projects, per workflow-core spec §13. When invoked on a new TS module, produces three ATOMIC commits in order: Phase 1 — declaration: a `declare`-only type-surface file (`<name>.declare.ts`). No implementation bodies, no expression initialisers, no executable code. Type- checks clean against `tsc --noEmit`. Phase 2 — tests: test files that import and exercise the declared surface. Tests MUST be observable as failing in the expected way at this commit (declarations exist, implementations don't). The expected-failure runner output is §06 evidence. Phase 3 — implementation: signatures match the declaration exactly. Tests now pass; commit captures the transition. The skill REFUSES to bundle Phase 1 and Phase 3 into a single commit. The three-commit atomicity is the structural evidence that the discipline was followed; coll
synthetic test fixture for migration 0009 — before-fresh
synthetic test fixture for migration 0009 — before-inlined-customised
synthetic test fixture for migration 0009 — before-inlined-pristine
