lifesg/wai

Principal engineer code review workflow — orchestrates 5 specialized review subagents plus always-on security verification and a second synthesis pass for comprehensive analysis covering security, architecture, production readiness, code standards, and strategic impact. Supports 3 scope strategies: DIFF (MR/PR/branch/pre-commit), TOPIC (feature or module name), and EXPLICIT (file list). Load when the user asks to review code, a merge request, a PR, a feature, or a file.

Guide for creating, reading, updating, or deleting skills, agents, or instruction files. Use when a user wants to add a new skill, build a new agent, contribute to the WAI plugin, or make any CRUD change to Copilot customization files — regardless of how the request is phrased (e.g., "create an agent", "edit my skill", "add a skill to WAI", "update an agent", "delete a skill", "modify an instruction file").

Enhancement Proposal (EP) creation — stepwise, KEP-style EP authoring with template discovery, parallel codebase research, and structured Part-1 / Part-2 / Part-3 generation. Use when creating or drafting an EP or feature design document.

Product Requirements Document (PRD) creation for product managers — guided feature-brief authoring, JIRA-format epic/story generation, and sprint-ready work breakdown. Use when writing feature requirements, creating JIRA tickets, or decomposing a feature into deliverable chunks. Integrates as optional Phase 0 of the WAI Maestro workflow.

Flagship Design System (FDS) knowledge for @lifesg/react-design-system — component catalogue, token reference, and Figma-to-FDS mapping heuristics. Use when implementing UI with FDS components or analysing which Figma elements can be fulfilled by FDS.

Create a new full-stack application with Vite + React + Flagship Design System frontend and Koa + PostgreSQL backend, all in a single project folder. Use when the user wants a full-stack app with a database, or asks for a project with both frontend and backend.

Atomic commit workflow — groups changed files into logical commits and produces Conventional Commit messages prefixed with branch name and author initials. Use when performing any git staging, committing, or when the user asks to save, commit, or push work.

Implementation plan generation — decomposes an EP or task description into a parallelised, phase-based workplan with a Mermaid dependency graph, critical path analysis, per-task agent prompts, and a parallel dispatch table. Use when creating an implementation plan for an EP or any task description.

GCC deployment via Rabbit Deploy — initialize a local project with git, configure the Rabbit Deploy GitLab remote with a Project Access Token, and push to trigger automatic deployment. Use when a user wants to deploy their project to GCC using Rabbit Deploy, set up version control for the first time, or push code changes to trigger the CI/CD pipeline.

Guide non-developers through software engineering workflows. Use when someone who works alongside developers (PM, designer, team lead, QA manager, technical writer) asks how to perform an engineering activity — making a feature change, fixing a bug, or requesting a code review.

Initialize a new Vite + React + TypeScript frontend project with Flagship Design System (@lifesg/react-design-system) pre-configured. Use when user wants to scaffold a new web application using FDS components.

Playwright setup and test authoring for any web application. Use when setting up Playwright from scratch, fixing a misconfigured Playwright project, or writing new spec files. Triggers on: "set up Playwright", "initialise E2E", "Playwright not working", "write a test", "add test coverage", "create a spec", "E2E tests".