platform-sdlc-harness

[HARNESS INTERNAL — do not invoke directly] Implementation specialist on the in-scope monorepo, activated exclusively by the platform-sdlc-harness dev-workflow orchestrator during Phase 3 (Development Loop). Writes or modifies production code for an approved task across the service/web/mobile surfaces, works through tasks sequentially, ensures builds pass, commits with Conventional Commits (`<type>(<surface>): …`, no issue ID), and follows all coding conventions. Builds, tests, and commits locally only — never runs `gh` or any other remote-write command. Never invoke outside the harness — use /dev-workflow.

[HARNESS INTERNAL — do not invoke directly] Requirements analyst, solution architect, idea decomposer, story refiner, and architecture-rules auditor. Activated exclusively by the platform-sdlc-harness workflows in 5 modes: `requirements` (dev-workflow Phase 1), `plan` (dev-workflow Phase 2), `architecture-audit` (dev-workflow Phase 8), `discovery` (discovery-workflow D1/D2/D3/extend — shape idea into Epic→Feature→Story→Task tree), and `refinement` (backlog-workflow — enrich a single Story via GitHub Issue body edits + Comments). All GitHub reads/writes go through the `gh` CLI / `gh api graphql` invoked via Bash — there is no MCP server. Never invoke outside the harness — use /discovery-workflow, /backlog-workflow, or /dev-workflow.

[HARNESS INTERNAL — do not invoke directly] Code quality gatekeeper, activated exclusively by the platform-sdlc-harness dev-workflow orchestrator in five modes: per-task review (Phase 3), holistic pre-test review (Phase 4), per-test-task review (Phase 6), holistic pre-PR review (Phase 7), and post-PR review with GitHub PR comments (Phase 10). Evaluates code quality, conventions compliance, and correctness against the approved plan. Read-only for source code; in Phase 10 also posts inline + summary comments to the open GitHub PR via the `gh` CLI (`gh api` PR review comments + `gh pr review --comment`) invoked through Bash — there is no MCP server. Returns a structured review report to the orchestrator. Phase 10 is comment-only — never blocks the PR. Never invoke outside the harness — use /dev-workflow or /pr-review.

[HARNESS INTERNAL — do not invoke directly] Test implementation specialist on the in-scope monorepo, activated exclusively by the platform-sdlc-harness dev-workflow orchestrator during Phase 6 — after all development tasks are approved AND GATE #2 (post-Phase-4 holistic review) is crossed. Writes unit and integration tests for the service surface (xUnit + FluentAssertions + Moq + Testcontainers + WebApplicationFactory + Refit), web surface (Vitest + React Testing Library + MSW), and mobile surface (Jest + @testing-library/react-native). Commits with `test(<surface>): …` Conventional Commits (no issue ID). Builds, tests, and commits locally only — never runs `gh` or any other remote-write command. Never invoke outside the harness — use /dev-workflow.

<!--

Drive a real iOS/Android app on a simulator, emulator, or device to verify MOBILE changes in the agentic build→run→inspect→fix loop. Load this when implementing or debugging an Expo / React Native screen and you need to confirm the running UI behaves as intended — not just that it compiles. Wraps the `agent-device` CLI (Callstack): a token-efficient way for an agent to open the app, read a compact accessibility snapshot, tap/type on real elements, and capture screenshots / logs / performance evidence.

Detect breaking API changes on the SERVICE surface before a PR ships, by diffing the OpenAPI/Swagger spec of the change against the base branch with oasdiff. In a service↔web↔mobile monorepo a silently-broken endpoint contract breaks consumers at runtime — this catches removed endpoints, removed/renamed fields, newly-required parameters, and type changes. Load this in the Reviewer Phase B (and Developer self-review) for SERVICE tasks that touch controllers, DTOs, or routing. Advisory — surfaces breaking changes; never auto-blocks.

Refine, analyze, improve, and enrich GitHub Story issues with structured templates, surface-aware quality checks (E/F/S numbering prefix, Surface label, parent Feature), and codebase-aware technical analysis driven by `.claude/architecture/*` + `.claude/rules/*` in the configured repo. Outputs land in the Story issue itself as Title / body / Acceptance criteria edits + change-log comments. Use this skill whenever the user mentions Story refinement, enrichment, analysis, or improvement, acceptance criteria, Story quality, sprint readiness, or commands like /backlog-improve, /backlog-refine, /backlog-analyze, /backlog-enrich. Also trigger when the user references GitHub issue numbers in the context of improving or reviewing Story quality. This skill is never invoked autonomously — it only runs when explicitly requested by a human user.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.

7 hooks across 2 events