4,621 件 ・ 関連度順
[Project Management] Use for explicit project-owned tracker guidance (--mode=guide), or portable-engine work records, placement, linked concerns, lifecycle, evidence, acceptance and local status. Existing engine modes and bare inspect remain supported.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Turn an idea or existing canonical specs into a reviewed provisional spec or reviewed, readiness-checked, prioritized planned tasks and stories; stop before implementation. --from=idea|spec --to=spec|tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Build, extend, validate, and publish a ChatGPT Sites application whose durable database and backend functions run on Convex. Use when a user invokes $codex-sites-convex, selects this skill from the skill picker, asks for a ChatGPT Site backed by Convex, or asks to add Convex data, realtime queries, mutations, authentication, files, schedules, or actions to an existing ChatGPT Sites project.
日本語の概要は準備中です。原文の説明を表示しています。
Use when condensing, decondenseing, refactoring, or improving existing skills. Covers the full skill lifecycle from verbose → sharp → maintained.
日本語の概要は準備中です。原文の説明を表示しています。
Validate whether a feature request fits the existing codebase — check for duplicates, contradictions, scope creep, and architectural misfit
日本語の概要は準備中です。原文の説明を表示しています。
Use when extracting Voice-of-Customer themes from existing artefacts — GH issues, PR threads, Sentry patterns. Triggers on 'what are users saying', 'recurring complaints', 'top themes'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when decomposing a company objective into team OKRs, auditing a draft OKR tree, or stress-testing an existing one for measurability and laddering.
日本語の概要は準備中です。原文の説明を表示しています。
Edit an existing image — inpaint, background swap, variation — via providers that support it. Use when editing/modifying/inpainting an image or making variations.
日本語の概要は準備中です。原文の説明を表示しています。
When the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. 7 phases: interaction, responsiveness, accessibility. Inventory via existing-ui-audit.
日本語の概要は準備中です。原文の説明を表示しています。
Frontend design heuristics and the loop applying them: existing-ui-audit, brief, inventory, build, review. Use when building or changing any UI, not only when planning one.
日本語の概要は準備中です。原文の説明を表示しています。
Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for fe-design.
日本語の概要は準備中です。原文の説明を表示しています。
Route codebase-structure questions (who calls X, where used, change-impact) to an existing code-graph first: impact, tests-for, dead cheaper, never more precise; grep routine. Also 'call graph'.
日本語の概要は準備中です。原文の説明を表示しています。
Audit how a brand is currently expressed across touchpoints and flag drift from its defined tokens, voice, and strategy. Use to inventory and critique an existing brand before changing it.
日本語の概要は準備中です。原文の説明を表示しています。
Stack an existing or new git branch on top of another branch, restacking it in a git worktree when needed, then align the GitHub PR bases and stack metadata with `gh stack`. Use when invoked as `$git-stack` or when the user asks to stack or restack a branch or PR onto another branch.
日本語の概要は準備中です。原文の説明を表示しています。
Conception pipeline for Codex. Equivalent to the repository's Claude skill: detect epic/task/bug mode, then delegate to the existing repo agents and workflows. Usage: /analyse [<issue#>] [<description>]
日本語の概要は準備中です。原文の説明を表示しています。
Review-fix pipeline for Codex. Equivalent to the repository's Claude skill: collect review feedback, apply fixes through the existing review workflow, and prepare replies. Usage: /review [<issue#>|<PR#>]
日本語の概要は準備中です。原文の説明を表示しています。
Edit an existing PRD. Use when the user says "edit this PRD".
日本語の概要は準備中です。原文の説明を表示しています。
Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"
日本語の概要は準備中です。原文の説明を表示しています。
Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.
日本語の概要は準備中です。原文の説明を表示しています。
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Run the speckit implementation phase chunk-by-chunk in clean-context subagents, then review, then produce a final report. Picks up from an existing tasks.md.
日本語の概要は準備中です。原文の説明を表示しています。
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
The kpopper method: a knowledge record (GROUNDING.yaml) for work that gets revisited - what is known, where each piece came from, and what would make each conclusion wrong. Use when asked what kpopper is or how to keep a record, when choosing which kpopper skill fits a moment, or when no narrower one does. The occasions have their own skills: ground (read the record before answering), record (write what the work found), map (map existing materials), annotated-doc (a standalone HTML document with evidence), hub (the record's visual home), consolidate (hypotheses and merges), watch (background checks).
日本語の概要は準備中です。原文の説明を表示しています。
Annotated Documents: optional experimental application for standalone HTML with evidence. Use when the user explicitly requests Annotated Documents or a kpopper HTML document with evidence, refreshes an existing kpopper document, or has a standing preference for this application. Generic HTML requests do not select it. Install the HTML runtime before use. Not for the record's own page or an ordinary website. Requests come in any language.
日本語の概要は準備中です。原文の説明を表示しています。