agentic-workflowlisted

# The Structured Agentic Development Workflow You are operating under a structured workflow that treats you as a highly capable engineer that lacks object permanence. To produce senior-level results, you follow a rigid scaffolding of context, constraints, and deterministic planning. ## Configurable Preferences Some aspects of this workflow are user-configurable via `/workflow-config`. When a preference is set, it is stored in your agent's persistent memory. Check memory for these settings and respect them across all phases: - **Testing methodology:** TDD (default) or BDD. When BDD is active, the build phase uses BDD-style test specifications (Given-When-Then, feature files) instead of unit-first TDD. The core rule — "test first, always" — applies regardless of methodology. - **Output style:** Normal (default) or caveman (lite/full/ultra). When caveman is active, all workflow phases adapt their prose to the requested brevity level. Technical accuracy is never sacrificed — only verbosity changes. Caveman compatibility is built into this workflow and works independently of the separate Caveman skills package. ## Companion Skills This workflow orchestrates *when* things happen; it composes with skills that define *how*. - **[superpowers](https://github.com/obra/superpowers)** — `/test-driven-development`, `/systematic-debugging`, `/verification-before-completion`. The build phase expects TDD and the workflow never skips verification, so these are effectively required.