「complete」の検索結果

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

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

Code comment accuracy verification, documentation completeness assessment, comment rot detection.

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

Extract knowledge, guidelines, and ADRs from one or more completed spec directories into the project documentation system.

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

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

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

Auto-commit changes after a Spec Kit command completes

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

Code comment accuracy verification, documentation completeness assessment, comment rot detection.

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

Creates complete newsletter editions for the Flow Factor Newsletter on Beehiiv. Generates full newsletter text (1,200-1,500 words), SEO metadata, subject lines, header illustration prompts, and NotebookLM audio briefing prompts. Use when user asks to write a newsletter, create email content, plan newsletter editions, or produce Beehiiv-ready content.

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

Manages brand identity, visual design system, and creative quality for MMIND.ai. Generates complete image prompts for Nano Banana Pro (Gemini), enforces the strict 5-color palette, flat-vector SaaS style, and typography standards. Use when user needs graphic prompts, brand consistency checks, visual style guidance, design briefs, or creative QA for any marketing asset.

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

Creates LinkedIn posts, thought leadership content, and editorial calendars for SME marketing. Covers 7 post types (Awareness, Personal Story, Education, Conversion, How We Do It, Building In Public, Lead Magnet) with complete graphic prompts, first comments, and CTAs. Use when user asks to write social media posts, plan content calendars, create LinkedIn content, or develop thought leadership pieces.

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

Assess development requests, then execute and resume complete TaskBelay tasks in ZCode with Core-owned state.

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

Assess development requests, then execute and resume complete TaskBelay tasks in Claude Code with Core-owned state.

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

Systematic testing methodology for exhaustive branch coverage, edge case identification, and production bug prevention. Use when PR review reveals incomplete test coverage, when tests pass but users report bugs, when code changes break existing features, when verifying all branches and edge cases before merge, when analyzing "it works on my machine" issues, when planning test strategy for new features, or when debugging flaky tests and race conditions.

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

Package completed data analysis and ML work so an independent recipient can reproduce the claimed results, verify artifact lineage, and operate the handoff within its stated scope. Use when finalizing a project, study, model package, or review bundle; not for deploying to a live system.

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

Bootstrap or harden a project's operating model for mixed human and AI delivery teams. Use when starting a repository, adopting an agent harness, defining authority and risk tiers, coordinating parallel agents safely, binding evidence and review to an exact candidate, or correcting fragmented rules that prevent coherent, consistent, complete delivery.

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

JP's signature red-team pass — "how would I break this?" Argue against your own approach before proceeding. Trigger on any high-stakes decision, architecture choice, or before marking work complete.

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

Re-audit code changes to identify side effects, regression risks, and unhandled edge cases before merging or deploying. Use after a change is complete and before merging to a shared branch, before deploying a hotfix, after complex multi-module refactoring, or when a previous review may have missed side effects in async, state-mutating, or security-sensitive code paths.

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

Ship an already-committed Git branch through GitHub: verify branch/worktree intent, push, create or mark a pull request ready for review, optionally wait for CI, optionally address review comments automatically, and merge with explicit safety gates. Use when a solo developer repeatedly asks to publish committed work, register a ready PR, handle PR feedback, and complete merge.

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

Use when the feature is implementation-complete and the next step is 'ship it' — verifies, cleans up, routes to merge/PR/park/discard; never destroys work without explicit confirmation.

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

Coordinate material messages between explicitly selected desktop-backed agents, including Claude, Codex and bb. Separates exact inbox delivery, native task wake, receiver ACK and completed work.

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

Publish a new Canvas Notebook release. Use this skill whenever the user asks to bump a version, prepare release notes, update CHANGELOG.md, create or push a git tag, publish a GitHub Release, deploy, or automate the release workflow. This skill covers the full release sequence for this repository: inspect commits/tags, push completed product-code commits first when authorized, confirm the pushed code has built on GitHub, choose the next calendar version, update package and CLI versions, update the changelog, run the required local build, commit, push the release commit, wait for the remote Build and Push worker on the pushed branch, tag, push the tag, and publish the release.

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

Load this skill when building any web feature, reviewing architecture decisions, or evaluating JavaScript dependencies. Under no circumstances build features that break completely when JavaScript is unavailable or fails. Absolutely always start with semantic HTML, layer CSS enhancements, and add JavaScript as the final, optional layer. Prioritize resilience and universal access over cutting-edge features.

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

[Workflow] Use when you need to run /workflow-review-changes repeatedly in an outer convergence loop until a complete whole-workflow run applies zero fixes — recursive re-review of a fixed scope (branch-diff + current changes) until a clean no-op pass.

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

[Workflow] Use when activating the Spec to PBI Backlog workflow to convert canonical tech-free Feature Specs into complete, prioritized, dependency-aware PBIs and stories.

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

[Process] Use when the developer wants something explained or taught, or wants to know HOW TO REVIEW a change — by default the current working tasks + changes in context, or whatever the prompt names (a plan, a subsystem, a decision, a concept, a bug). AI derives WHAT to explain from the prompt and ALWAYS delivers a teacher-and-coach review guide, high level first then detail: what was done, a VISUAL MAP (system flowchart, domain ERD, sequence diagrams), the user stories and business rules with their REAL test-case IDs, a REVIEW PATH naming which files to open first and in what order with an exit criterion per stage, the technical concepts needed to follow it, how it works, why THIS solution, every alternative option with pros/cons, the trade-offs accepted, the blast radius, HOW TO TEST AND DEMO the change, the developer's decision levers, and written challenge prompts that provoke the reader to pressure-test the work. Works at ANY scope — from one line of code to the whole project: it SIZES the target into a scope tier, DECOMPOSES a large one into understanding groups, BREAKS the work into tasks before the first deep read, and ACCUMULATES the report group by group on disk so a huge explanation stays complete instead of thinning out. Writes the full report to a single combined markdown file (plans/reports/understand-*.md) that opens with a detailed summary section — or delivers it in full in chat when Step 3 finds no git-ignored directory for it — and always summarizes it in chat. Regardless of coding level. Never interrogates, never quizzes, never blocks.

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