「backlog」の検索結果

Review and promote backlog items to active milestone

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

Add an idea to the backlog parking lot (999.x numbering)

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

Use when asked to build a product roadmap, prioritize a backlog, decide what to build next, or sequence a list of feature ideas. Examples: "what should we build next", "prioritize this backlog", "make a roadmap", "RICE score these features".

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

Routes a Superpowers plan file through the /work-backlog-item pipeline and writes SAM task back-references and chunk annotations into the original plan. Use when given a path to a Superpowers plan file via $ARGUMENTS and needing to create a linked backlog item plus SAM task plan.

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

Register a plan artifact via the MCP backlog server. Use when you produce a document or report that downstream agents or worktree-isolated environments need to retrieve — feature-context, codebase-analysis, architect, T0-baseline, TN-verification, or research artifacts. Triggers include "store an artifact", "register a plan artifact", "write a report to the backlog", "upload artifact content".

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

Assign backlog items to a GitHub milestone by bridging per-item files to GitHub Issues. Use when populating a sprint or release milestone, after create-milestone, or when a milestone number is specified with optional P0/P1/P2 or title filter. Creates missing GitHub Issues for selected P0/P1 items, assigns all selected items to the milestone, and updates Project V2 Status to Backlog.

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

The Mileva Method (CRISP) — Phase 4: Spec. Full implementation readiness package including solution design, UX direction, tech stack, backlog, MVP prioritization, risk assessment, and AI architecture for Claude Code projects — CLAUDE.md, skill mapping, AI specs, sprint planning, quality gates. Triggers on "spec", "phase 4", "build ready", "implementation plan", "CLAUDE.md", "sprint planning", "backlog", "AI spec", or after Phase I exit checklist is complete.

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

Survey the whole tdmcp project and produce a prioritized list of NEW features it could implement — across artist controls, CLI/DX, AI/LLM integration, and TouchDesigner depth. Use whenever the user wants to brainstorm, discover, survey, list, or audit what features/tools/effects/controls/commands/prompts/capabilities tdmcp *could* add, asks 'what could we build / what's missing / what are the opportunities / ideas for the project', or wants a feature backlog or gap analysis. Also for follow-ups: re-run, refresh, update, re-survey, deepen, or re-prioritize the backlog, or survey just one surface (e.g. 'CLI ideas only'). This is the IDEATION harness — it produces a list to decide from; it does NOT build. When the user has already chosen a feature and wants it implemented/shipped/added, use tdmcp-pipeline instead.

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

Scout the TouchDesigner community for what's HYPED right now — community showcases, recent tutorials, generative-AI bridges, hardware interaction trends, visual-aesthetic trends of 2025-2026 — then propose tdmcp tools that ride those trends AND are easy to build. Use whenever the user wants to brainstorm new feature ideas based on what's trending in TouchDesigner, asks for 'hype' or 'trending' features, asks 'what are people doing in TD right now / what's hot / what's hype', wants tools inspired by community trends, asks to scout TD trends/aesthetics/integrations, or says things like 'ideias hype', 'novas ideias', 'o que está em alta', 'criar ferramentas para o que está bombando', 'tendências do TouchDesigner'. Also for follow-ups: refresh, rescout one surface, re-rank under another profile, deepen a trend, or filter for buildable-easy items. This is an EXTERNAL trend ideation harness — complementary to tdmcp-feature-discovery (which is INTERNAL gap analysis). It produces `_workspace/hype-scout/HYPE_TOOL_BACKLOG.md` ranked by Hype × Build-Ease; it does NOT build. Once a feature is chosen from the backlog, hand it to tdmcp-pipeline.

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

Use when the user dumps a batch of inputs at once — a pile of emails, a backlog of Slack/Teams messages, a list of asks, meeting action items, a notes brain-dump — and needs it sorted into action. Classifies each item, assigns owner + next step + priority, and flags which need a full /structure brief or a /decide call. Trigger on "/triage", "triage this", "process my inbox", "sort these asks", "clear my backlog", "what do I do with all this".

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

AI-PLC Stage 2 Inception。IntentとContextからGoalを分析し、BacklogとSub-Agent Registryを生成する。

ai_plc_inception - AI-PLC Stage 2。Goalを分析し、BacklogとSub-Agent Registryを生成する。

AI-PLC Stage 4 Operation。Backlog（Agent定義があればそれ）に従ってタスクを実行し、成果物生成、検証、ステータス更新、Propagationを行う。

AI-PLCのスキルを通さずに済ませた作業を、あとから対象Layerに記録する（書き起こし・backlogへad-hocで追加・04-operation Phase 5.5〜7で検証後にcompleted）。書き込み前に承認を取る。

AI-PLC Stage 1 Collection。GoalとModeからExecution Contextを確立し、Context Store、intent.yaml、context.yaml、backlog.yamlを生成する。

AI-PLCのステータス点検。intent.yaml・backlog.yaml・Registry の食い違い（閉じ忘れ・Layer不明・停滞・Registry漏れ）を読み取り専用で洗い出し、人が承認した行だけ反映する。「ステータス点検して」「閉じ忘れを探して」「食い違いを見て」で使う。Jev 実験版（--with-jev）を入れたときだけ使える。

【実験版・Jev監視つき】ai_plc_operation - AI-PLC Stage 4。backlog（Agent定義があればそれ）に従ってタスクを実行し、成果物をArtifact Storeに格納する。

AI-PLCのステータス点検（intent・backlog・Registry の食い違い）。Jev 実験版を入れたときだけ使える。

議論・議事録・選定された施策を起点に、対象リポジトリの実構造にgroundした「エンジニア向け Story（User Story + Acceptance Criteria）と Spec（技術仕様）」をSubagentで収束生成する。target_repoで対象コードベースを、backlog_db_urlで起票先バックログを選べる汎用スキル。抽象的な打ち手を実装可能な仕様へ絞り込む収束フェーズの実行に使う。

ai_plc_operation - AI-PLC Stage 4。backlog（Agent定義があればそれ）に従ってタスクを実行し、成果物をArtifact Storeに格納する。

AI-PLCの進行中に、ユーザーの「ここをこうしたい」を命令ではなく相談として受け、今のLayer（intent・backlog）と照らして「却下／今のタスク内で修正／Re-Inception／Re-Collection／いつかやる」に振り分け、所感と次に打つコマンドを返す（読み取り専用・実行しない）。「どう思う？」「これやるべき？」「Inceptionからやり直すべき？」「次どのコマンド打てばいい？」で使う。

Plan a sprint by refining backlog items, defining a sprint goal, calculating team capacity, selecting items, and decomposing them into tasks. Produces a SPRINT-PLAN.md with goal, selected items, task breakdown, and capacity allocation. Use when starting a new sprint in a Scrum or agile project, re-planning after significant scope change, transitioning from ad-hoc work to structured sprint cadence, or after backlog grooming when items are ready for inclusion.

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

Use when the user invokes backlog triage for a GitHub repo's open issues and PRs. Not for proactive triage, non-GitHub trackers, or single bug issues: use github-bug-report-triage.

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

Use when evaluating whether a bug issue has sufficient detail and identifying missing reporter information. Not for non-bug issues or backlog triage: use github-backlog-triage.

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