「planning」の検索結果

[Planning] Use when you need to validate a plan with critical questions interview.

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

[Planning] Use when the user provides an implementation plan file and asks to analyze it, assess impact, update specifications, or verify planned changes.

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

[Planning] Use when you need to start a new project from scratch with full waterfall inception — idea, research, domain modeling, tech stack, and implementation plan.

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

[Planning] Use when calibrating estimates from actual code, diff, PR scope, and developer time.

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

Plan modeや計画作成・プラン作成の依頼時に必ず発動し、必須セクションを漏れなく含む計画を作るためのガードレールを提供します。参考情報（URL/過去PR/ファイルパス）とユーザー発言（要約＋生ログ）を必須化し、テストがある場合はTDD前提と正常系/異常系テストケース記載を強制します。

Project-level WeChat article drafting workflow for turning source materials, repo intakes, product notes, screenshots, or existing markdown into a publishable Chinese公众号 draft. Use for writing, rewriting, evidence-gating, title options, platform adaptation, and image planning before optional publishing.

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

Project-level visual direction skill for WeChat Official Account articles. Use when planning, improving, diversifying, generating, or reviewing cover images and body illustrations for公众号文章, especially when Codex image generation should be used without being constrained by repetitive preset-based illustration skills.

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

Use when auditing or fixing prose that reads like a leaked reasoning transcript — dead design-session citations such as (decision N), audit item codes, or §N of uncommitted drafts; change narration such as "used to", "no longer", "this cut"; stack or review vantage ("a later PR in this stack", "rejected in review"); reviewer-addressed justifications; control-flow narration; or hedged planning residue in comments, JSDoc, docs, or Agent Notes.

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

Use when a HyperFrames composition needs a punch-in, punch-out, zoom, reframe, Ken Burns treatment, camera move, visual match/whip handoff, or other seek-safe 2D/3D keyframes; also for GSAP, CSS keyframes, Anime.js, WAAPI, FLIP, paths, masks, SVG morph/draw, text trails, 3D depth, or `hyperframes keyframes` diagnostics. Don't use for broad scene strategy, brand design, media sourcing, captions, or general video planning.

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

Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-animation`.

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

Generate sitemap and wireframe specifications from project-config.json and produce UX planning artifacts.

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

Run frontend functional, accessibility, visual, and performance test planning with structured reports.

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

Design, audit, harden, review, or upgrade MCP servers and MCP Apps with revision-aware protocol profiles, explicit HTTP/deployment boundaries, capability-centered validation, bilingual reporting, and reproducible evidence. Use for MCP server architecture, JSON-RPC or Streamable HTTP bugs, security hardening, protocol-version migration, MCP Apps widget boundaries, review reconciliation, test planning, and public engineering evidence.

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

Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or parallelizable task breakdown.

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

Use this skill when planning, redesigning, or reviewing Xiaohongshu carousel visuals, covers, 3:4 image posts, page-by-page visual direction, image-generation prompts, style selection, layout critique, or XHS captions. It acts as a senior visual director for 小红书图文, not a generic copywriting assistant.

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

Read and analyze Xiaohongshu comments from the user's signed-in Chrome session. Use to collect, export, summarize, or classify comments for content planning, follow-up posts, audience research, reply strategy, and 引流文案。

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

GStack deployment setup method for planning environment, config, secrets, build, deploy, and verification gates before release operations.

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

GStack land-and-deploy method for explicit landing and deployment workflows with tests, release notes, rollout gates, and rollback planning.

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

GStack design-html method for producing or planning quick HTML prototypes, design boards, or rendered visual explorations for UI review.

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

SOP for the architect-tier campaign workflow (/campaign): exhaustive survey, mitigation planning, tiered orchestration, and reconciliation. Trigger when: - Running a multi-workstream initiative where an expensive architect-tier council surveys, plans, emits worker prompts, and judges landed work. - Conducting production-readiness assessments that fan out into autonomous mitigation dispatches across model tiers. - Prompt contains: /campaign, campaign workflow, survey, orchestrate, reconcile, premise freshness, tier routing, worker IBC, scratch.

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

Track work as GitHub issues in this monorepo — create epics + child/sub-issues, label them consistently by package/app, and tie them into the commit workflow. Use when planning a feature, breaking work into tasks, or asked to "track this in GitHub", "make issues", "set up tracking".

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

Data Scientist role within the AID methodology. Activate when working on: EDA, feasibility assessment, experiment planning, ML architecture, model development & validation, or production deployment & monitoring. Stack-agnostic — ask the user for their stack at the start of any new project.

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

AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.

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

Central entry point of the afonsoft agent harness. Use when starting a new project, resuming an existing one, planning features/Epics/releases, or running any multi-step agent-driven work. Validates and reconciles SPECs (SDD), audits the codebase and harness for gaps (security, architecture, performance, hygiene), proposes improvements, fragments work into GitHub Issues, delegates implementation/QA/review to specialized skills, and re-validates everything until delivery. Also use to review unapproved SPECs, reconcile open GitHub Issues with code, or run a final gap check before closing a release.

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