「requirements」の検索結果

Break requirements into epics and user stories. Use when the user says "create the epics and stories list"

日本語の概要は準備中です。原文の説明を表示しています。

Create a PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"

日本語の概要は準備中です。原文の説明を表示しています。

Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.

日本語の概要は準備中です。原文の説明を表示しています。

Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.

日本語の概要は準備中です。原文の説明を表示しています。

Generate a custom checklist for the current feature based on user requirements.

日本語の概要は準備中です。原文の説明を表示しています。

Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.

日本語の概要は準備中です。原文の説明を表示しています。

Generate a custom checklist for the current feature based on user requirements.

日本語の概要は準備中です。原文の説明を表示しています。

GitHub Pull Request creation specialist. Analyzes user requirements to create PRs with structured titles and bodies matching the user's query language. Handles git change analysis, PR draft creation, user confirmation, and final PR creation via gh CLI.

日本語の概要は準備中です。原文の説明を表示しています。

Load this skill whenever the project contains in-page anchor links, skip links, fragment identifiers, or heading links. Under no circumstances omit accessible anchor-link requirements when such links exist. Ensure every anchor link has meaningful text, a reachable target, and a visible focus indicator. Apply these rules when creating or reviewing any in-page navigation.

日本語の概要は準備中です。原文の説明を表示しています。

Load this skill whenever the project contains interactive UI elements that users touch, tap, click, drag, swipe, or gesture with — buttons, links, drag-and-drop interfaces, sliders, carousels, or custom touch interactions. Under no circumstances create touch targets smaller than 44×44 CSS pixels. Absolutely always provide pointer cancellation, single-pointer alternatives to gestures, and load alongside keyboard/SKILL.md since pointer and keyboard requirements are complementary.

日本語の概要は準備中です。原文の説明を表示しています。

[Project Management] Use when converting ideas to PBIs, validating problem hypotheses, adding acceptance criteria, or refining requirements.

日本語の概要は準備中です。原文の説明を表示しています。

[Project Management] Use when creating user stories from PBIs, slicing features, or breaking down requirements.

日本語の概要は準備中です。原文の説明を表示しています。

[Project Management] Use when creating user stories, writing acceptance criteria, analyzing requirements, or mapping business processes.

日本語の概要は準備中です。原文の説明を表示しています。

[Project Management] Use when you need to create UI/UX design specifications from requirements, PBIs, or user stories. Use --mode=wireframe to convert hand-drawn/digital wireframes or UI sketches into structured specs.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluates candidate profiles against a job description and hiring criteria. Use when the user provides candidate profiles plus a role definition and wants consistent screening, matched requirements, and an interview recommendation.

日本語の概要は準備中です。原文の説明を表示しています。

Translate designs and UI requirements into robust, extensible implementations. Apply when converting designs to code, implementing components, fixing broken UI, or handling responsive layouts.

日本語の概要は準備中です。原文の説明を表示しています。

Update an existing GitHub Issue's description based on the issue number. Reads all issue comments and reflects any items not yet captured in the description. After refreshing the description, reviews it for remaining ambiguities or unclear requirements and posts any open questions as a follow-up 確認事項 comment.

日本語の概要は準備中です。原文の説明を表示しています。

Use when you have a spec or requirements for a multi-step task, before touching code

日本語の概要は準備中です。原文の説明を表示しています。

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Builds and improves task-specific decision artifacts from application requirements and labeled records. Use for data assembly, primitive and base-model selection, fitting, export/reload, inference policy, or bounded data/model/program improvement. Includes rules and no-training outcomes; does not require a rung ladder or training a general Jev.

日本語の概要は準備中です。原文の説明を表示しています。

Initialize or repair the GEO-SEO Codex runtime for plugin and classic installer modes. Creates a Python virtual environment, installs requirements, verifies bundled scripts/templates, and explains optional PDF/browser dependencies.

日本語の概要は準備中です。原文の説明を表示しています。

Idiomatic programming style, patterns, and conventions for Python development. Trigger when: - Writing, refactoring, reviewing, or debugging Python code. - Files matching the pattern **/*.py (including requirements.txt, pyproject.toml, setup.py) are in the workspace or referenced. - Tasks involve: python, pytest, pip, uv, virtualenv, flake8, black, mypy. - Prompt contains keywords: python, py, pep8, typing, list comprehension, decorator, generator, asyncio, yield, poetry.

日本語の概要は準備中です。原文の説明を表示しています。

PM role in AID methodology. Use for requirements, user stories, acceptance criteria, stakeholder management, scope definition.

日本語の概要は準備中です。原文の説明を表示しています。