「phases」の検索結果

Display project statistics — phases, plans, requirements, git metrics, and timeline

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

Generate UI design contract (UI-SPEC.md) for frontend phases

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

Interactive command center for managing multiple phases from one terminal

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

Insert urgent work as decimal phase (e.g., 72.1) between existing phases

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

Initialize a new project using Documentation-Driven Development. Research, then write user-facing docs (SPEC.md) as the spec, then user validates docs, then phases derive from doc sections. Best for CLIs, libraries, SDKs, APIs, plugin systems, anything with a well-defined user-facing surface.

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

Generate AI design contract (AI-SPEC.md) for phases that involve building AI systems — framework selection, implementation guidance from official docs, and evaluation strategy

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

Create phases to close all gaps identified by milestone audit

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

Run all remaining phases autonomously — discuss→plan→execute per phase

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

End-to-end production workflow guidance for Blender — the order to assemble scenes (block-out → camera → light → forms → materials → detail → render → composite → export), critique protocols, time budgets, and recovery patterns. Use whenever the user asks to "make a complete scene / hero shot / production-quality render", "what's the right order to do this", "set up a full pipeline", or has a multi-step request crossing modeling + lighting + materials + rendering. Make sure to use this skill for any request that spans multiple phases of 3D work, even if the user does not say "workflow" — also covers "make a final image of X", "produce a hero render", "professional-looking result".

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

Generate scaffolds supporting student self-regulation across planning, monitoring, and evaluation phases. Use when students struggle to manage their own learning during extended or independent tasks.

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

Use when the user asks "what should I work on", mentions GSD phases, ROADMAP, or .planning/ artifacts. Routes to the correct GSD command for the current project state.

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

Project state awareness and session recovery for GSD-managed projects. Use this skill whenever: starting a new work session, resuming after a break, the user asks "where did we leave off" or "what's the current state", before making substantial code changes (to check for existing plans), the user seems disoriented about project status, or when something seems off and STATE.md might have relevant context. Also activates when the user references .planning/ files, milestones, phases, or project progress.

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

The creative process in art from idea to exhibition. Covers five phases of creative work (inspiration, incubation, exploration, execution, reflection), sketchbook practice, artist statements, critique methodology (formal and conceptual), portfolio development, and the studio as a working environment. Use when guiding students through project development, facilitating critique sessions, developing artist statements, curating portfolios, or understanding how professional artists structure their creative practice.

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

NASA Systems Engineering methodology mapped to cloud operations. Use when planning, executing, verifying, or documenting OpenStack cloud infrastructure following NASA SP-6105 and NPR 7123.1 processes. Provides phase gate criteria, document templates, and cross-references for all 7 SE lifecycle phases applied to cloud deployment and operations.

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

Start a complete plugin refactoring workflow that analyzes plugin structure, creates a refactoring plan with tasks, and guides through execution. Use when you need to refactor an entire plugin — triggers assessment, design, planning, and parallel agent execution phases.

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

Decide which plugin component type to use and how to organize components at scale. Covers the component lifecycle (discovery and activation phases), decision framework for choosing between commands, skills, agents, hooks, and MCP servers, and organization patterns for each component type. Use when asking "which component type should I use", "command vs skill vs agent", "when to use a hook vs MCP server", "component lifecycle", "how to organize plugin components", "plugin structure patterns", or "scale a plugin with many components".

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

Transforms validated /linear-walkthrough artifacts into one presentation-ready deck outline per major codebase component. Use when the user asks to create a presentation, prepare a walkthrough deck, build an onboarding deck, produce an architecture review deck, or summarize a codebase for a technical audience. Requires walkthrough directory output -- reads unified walkthrough, per-section files, validation reports, coverage maps, entry points, and open questions -- then orchestrates four parallel agent phases to produce slide outlines with speaker notes, evidence references, and suggested visuals.

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

Decompose substantive work into phases, dispatch each phase to a sub-agent, and adjudicate what comes back. Use whenever a request asks for implementation, investigation, a fix, a review, or any change to files — including small ones — and whenever you are about to read source or run a diagnostic yourself instead of handing it off. Also use when a report from a sub-agent needs judging, when a phase needs re-dispatching, or when a user names one instance of a pattern. Does not apply when your own prompt begins "Your ROLE_TYPE is sub-agent." — then follow references/sub-agent-contract.md instead.

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

Produces a structured, end-to-end linear walkthrough of an unfamiliar codebase by orchestrating parallel subagents across four phases — discovery, tracing, validation, and synthesis. Use when onboarding to a new repository, understanding execution paths from entry points, generating navigable codebase documentation, or needing fact-checked coverage of architecture, deployment, testing, and operations.

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

Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.

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

OCRs scanned or image-only corpora with vision-language models in three phases. Evaluate selects a system by measured CER or WER against stratified human ground truth. Run builds the production pipeline. Clean corrects raw OCR with LLM and rule-based passes, quality diagnostics, and span-level provenance. Use when choosing an OCR model for a corpus, measuring OCR accuracy, transcribing scans at scale, or correcting raw OCR. Born-digital documents with text layers go to doc-to-markdown.

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

OCR scanned or image-only corpora with vision-language models in three phases: `evaluate` picks a system by measured CER/WER against stratified human ground truth, `run` builds the production pipeline, and `clean` corrects raw OCR with LLM and rule-based passes, diagnostics, and span-level provenance. Born-digital documents with a text layer go to $doc-to-markdown.

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

Guide a PACK-X author through the SPF fill cycle 01-11. Calls R28 Diagnostician to select mode (assembly/hybrid/full SPF) and leads through phases. Protects the read-only upstream invariant via PreToolUse hook.

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

Check agent configuration coverage across hierarchy levels and phases. Use to ensure complete agent system coverage.

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