4,215 件 ・ 関連度順
概要と使いどころ
Evaluates take-private feasibility with premium analysis, financing capacity, governance considerations, and regulatory requirements. Use when analyzing take-private opportunities, modeling go-private premiums, or assessing delisting mechanics.
日本語の概要は準備中です。原文の説明を表示しています。
Maps competitive dynamics with market positioning, feature comparison, funding histories, and differentiation assessment. Use when analyzing startup competition, mapping market landscapes, or identifying competitive threats.
日本語の概要は準備中です。原文の説明を表示しています。
Implement features, fix bugs, and keep the codebase healthy and maintainable. Works from a defined PBI, issue, or task description.
日本語の概要は準備中です。原文の説明を表示しています。
Create, reverse-engineer, or update living feature specs following the spec-anchored methodology.
日本語の概要は準備中です。原文の説明を表示しています。
Hunt vulnerabilities in LLM-powered applications — direct/indirect prompt injection, system prompt extraction, ASCII smuggling, RCE via code tools, agentic AI exploits (ASI01-ASI10), data exfiltration via response channels, IDOR in chat history, jailbreak chains, RAG poisoning. Use when target has a chatbot, AI assistant, copilot, or agentic AI features.
日本語の概要は準備中です。原文の説明を表示しています。
Create change specification and implementation plan with dynamic phase generation. Supports feature, bugfix, refactor, and epic types.
日本語の概要は準備中です。原文の説明を表示しています。
Intent-to-command mappings for fullstack-typescript tech pack features.
日本語の概要は準備中です。原文の説明を表示しています。
After an issue's PR has squash-merged on GitHub and its issue has closed: fast-forward the default branch, remove the issue-numbered nested worktree (.worktrees/<issue#>), and delete the local feature branch. Use when the user says to finish, tear down, or clean up a lane or worktree for a merged issue.
日本語の概要は準備中です。原文の説明を表示しています。
After /start-task: park the current clean, pushed feature branch in its own issue-numbered nested worktree (.worktrees/<issue#>) and return the primary checkout to current main, so the next parallel lane can start. Use when the user says to move the branch or task to a worktree or open a parallel lane.
日本語の概要は準備中です。原文の説明を表示しています。
Phase 1 of 5 — Socratic interview capturing WHAT and WHY; outputs a sprint-sized REQ doc for plan-architecture. Use only when the user asks to run Phase 1, plan requirements, or start the requirements interview — never trigger automatically from a feature description.
日本語の概要は準備中です。原文の説明を表示しています。
Bootstrap a task into a synced feature branch — one shot, zero confirmations. Detects the source from the args: GitHub issue ('#100', 'issue 100', 'gh issue 100', or bare '100'), Jira key ('PROJ-42'), or a local spec file path; ad-hoc conversation otherwise. Fetches the task, derives {type}/{number}/{slug}, syncs the default branch, creates and pushes the branch, and writes specs/context/<id>.md. Use only when the user explicitly asks to start a task or create a work branch — never trigger automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Format commit messages following conventional commits standard. Use when: writing commit messages, git commit, reviewing commit history. Keywords: commit, git, message, conventional, 提交, 訊息, feat, fix, refactor.
日本語の概要は準備中です。原文の説明を表示しています。
Refactor with tests first, one change at a time, never mix refactoring with bug fixes or new features
日本語の概要は準備中です。原文の説明を表示しています。
Complete feature development with structured options for merge, PR, or cleanup
日本語の概要は準備中です。原文の説明を表示しています。
Audit and realign UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system.
日本語の概要は準備中です。原文の説明を表示しています。
Reduce visual intensity, saturation, and noise while preserving hierarchy and character. Use when the structure is basically sound but the design feels too loud, bold, garish, aggressive, or overstimulating—not when the real problem is structural clutter, too many features, or not enough personality.
日本語の概要は準備中です。原文の説明を表示しています。
Create standout, technically ambitious interfaces that feel extraordinary through cinematic transitions, advanced motion, heavy rendering, or other high-ambition implementation work. Use when the user wants to wow, impress, go all-out, or push a feature beyond conventional UI polish—not when simple visual confidence or routine cleanup is enough.
日本語の概要は準備中です。原文の説明を表示しています。
Requirements gathering workflow for specification creation. Use when starting a new feature, task, or project that needs structured requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Strictly adheres to specified user flow and game rules, making sure to follow documented features.
日本語の概要は準備中です。原文の説明を表示しています。
React ecosystem expert including hooks, state management, component patterns, React 19 features, Shadcn UI, and Radix primitives
日本語の概要は準備中です。原文の説明を表示しています。
Customer feedback analysis — sentiment detection, NPS/CSAT frameworks, feature request clustering, support ticket triage, churn signal detection, and feedback-to-roadmap translation
日本語の概要は準備中です。原文の説明を表示しています。
Use when monitoring online forums (Reddit, HN, ProductHunt) for recurring user pain points, feature requests, and unmet needs. Invoke for market research, pain-point discovery, trend detection, and competitive intelligence. Designed for scheduled execution via CronCreate.
日本語の概要は準備中です。原文の説明を表示しています。
Instantiate a phase artefact (requirements-spec / design-spec / test-spec) from the Programme bundle's template into docs/specs/<feature-id>/. Refuses to overwrite existing artefacts.
日本語の概要は準備中です。原文の説明を表示しています。
Run a Programme phase gate validator (requirements / design / test / code) against docs/specs/<feature-id>/. Block on missing artefact or broken cross-phase reference.
日本語の概要は準備中です。原文の説明を表示しています。