ways-of-workinglisted

# Ways of Working ## Development Workflow Development is agent-first — every change starts as a structured issue and flows through issue → plan → implement → test → review: 1. **Create an issue** using the [devantler-tech/.github issue templates](https://github.com/devantler-tech/.github/tree/main/.github/ISSUE_TEMPLATE): - **Feature** — user story with acceptance criteria. - **Bug** — expected vs actual behavior with reproduction steps. - **Chore** — user story with acceptance criteria for general tasks. - **Kata** — Improvement Kata for continuous improvement (problem → definition of awesome → target condition → actions). 2. **Plan** — create a structured implementation plan from the issue before writing code. 3. **Implement** — execute the plan following the practices in this skill (TDD, quality gates, GitHub Flow, CI/CD). 4. **Manual test** — validate behavior hands-on before merging. Focus on UX: output must be well-presented and every piece of feedback (errors, warnings, prompts) must be actionable. 5. **Code review** (optional) — CI's strict linting, scanning, and quality gates are the primary feedback loop, so manual review is not always required. ## Testing Follow the [test-driven-development](https://github.com/obra/superpowers/tree/main/skills/test-driven-development) skill rigorously — write the test first, watch it fail, write minimal code to pass. ### Application / Library Repositories | Type | Tooling | When to run | |------|---------|-------