A coordinator for a software project from requirements through deployment. It assigns work to specialists such as product, architecture, development, testing, and operations agents, while recording decisions and required checks.
A method for researching and comparing technical options before choosing tools or an architecture. It covers trade-offs, existing open-source projects, performance information, and risks.
A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.
A requirements-clarification process for turning a vague idea into a written design brief. It asks business-focused questions about the users, problem, main task, and current situation before technical planning begins.
A method for creating a CHANGELOG, a document that records what changed in each software release. It reads Git commit history and release-pipeline reports, then groups changes using common commit and changelog conventions.
A guide to releasing software through automated build, test, and deployment steps. CI/CD means automatically checking code and moving it through environments such as development, staging, and production.
A guide for writing a PRD, or product requirements document: a shared document that explains what a product feature should do and why. It defines the goal, users, functions, priorities, competitors, and testable acceptance criteria.
A method for uncovering the needs behind a user's first request. It uses repeated questions about what, why, who, when, where, how, and cost to separate stated needs from unstated ones.
A business review method that evaluates whether a feature or project is worth pursuing. It considers market fit, return on investment, competitive advantage, risks, and alignment with company strategy.
A method for writing Playwright end-to-end tests, which automate a browser to verify complete user journeys. It covers setup, reusable page objects, login reuse, API mocking, visual checks, multiple browsers and screen sizes, CI, and debugging.
A testing strategy based on the testing pyramid: many small unit tests, fewer integration tests, and a smaller set of end-to-end tests that follow real user journeys. It also defines checks for security, boundaries, permissions, and business consistency.
A method for identifying project risks, rating their likelihood and impact, and choosing a response. Risks include technical problems, limited resources, unclear requirements, and unreliable outside services.