メニュー
Query the screen-map tree by frontmatter filter (e.g. "product:ppt,implementations.ppt-web.redesignStatus:in-progress"). Output as table, JSON, or markdown. Use when user runs `/screens query` or asks "which screens are X", "list all Y screens", "find screens with Z".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Implement one task end-to-end for the PPT project — pick the right per-stack specialist, code, verify per-stack, push a draft PR against `dev`.
Project-management & delivery analysis for the PPT research routine (Phase 1.6). Runs an always-on Scrum Master synthesis plus role-based deep analysis (rotating one role/day by default; all 8 on `full`; a specific role on `pm:<role>`). Reads sprint-status + repo activity + research backlog, spawns role subagents, and writes delivery artifacts under .research/management/. Use from routine Phase 1.6, or standalone for a delivery snapshot.
Post-merge code review with issue creation. Reviews merged PRs in a time window, spots better approaches / missed edge cases / security holes / perf issues / test gaps, and opens GitHub issues with concrete improvement proposals.
Deterministic goal/convergence checks for the PPT dispatcher — coverage referential integrity, coverage-progress monotonicity, and buffer bounds. Run in dispatcher Phase 6 and CI. Use when adding/auditing the dispatcher's goal-verification layer.
Open a PR in this project's style — title, body template, IG3 evidence, CI surface, draft handling.
Land a green, approved PR. Verify preconditions (CI green, approved, no unresolved threads, not draft), auto-resolve mechanical merge conflicts against the base branch (sqlx offline data, Cargo.lock, generated openapi/api-client, lockfiles), then `gh pr merge --squash --auto`. Stops and surfaces if real code conflicts or stale CI.
| name | screen-query |
| description | Query the screen-map tree by frontmatter filter (e.g. "product:ppt,implementations.ppt-web.redesignStatus:in-progress"). Output as table, JSON, or markdown. Use when user runs `/screens query` or asks "which screens are X", "list all Y screens", "find screens with Z". |
Read-only query against docs/screens/<product>/*.md frontmatter using the comma-AND key:value filter syntax (same as screen-map-review --filter).
/screens query <expr>.<expr> (positional; optional). Empty → returns all. Examples:
product:pptimplementations.ppt-web.redesignStatus:in-progressproduct:ppt,implementations.ppt-web.buildStatus:shipped--root <path> (defaults to repo root).--format <fmt> (table default, json, md).REPO_ROOT="$(git rev-parse --show-toplevel)"
pnpm -C "$REPO_ROOT/frontend" --filter @ppt/screen-map cli query "$EXPR" \
--root "$REPO_ROOT" \
${FORMAT:+--format "$FORMAT"}
N screen-maps matched.--format=md the output is paste-friendly; for --format=json it's machine-readable.| Goal | Expression |
|---|---|
| All PPT screens | product:ppt |
| Mobile screens still in progress | implementations.mobile.buildStatus:in-progress |
| Reality screens with redesign applied | product:reality,implementations.reality-web.redesignStatus:applied |
| Shipped but redesign not started | implementations.ppt-web.buildStatus:shipped,implementations.ppt-web.redesignStatus:not-started |
Filter syntax limit: comma-AND only (no OR). For more complex conditions, run multiple queries and intersect manually, or wait for Phase 3+ to add a richer query DSL.