Results for “spec”

Orchestrator for spec-driven development (SDD) — the discipline of writing executable specs before code, with a constitution above them and a hard cross-check gate before implementation. Mirrors GitHub Spec Kit / AWS Kiro slash-command shape. Routes /constitution, /specify, /clarify, /plan, /tasks, /analyze, /implement to the right leaf skill. Load when the user says "spec-driven development", "SDD", "specs-first workflow", "run the spec loop", "/specify a feature", "/plan from this spec", "do spec-driven for this", "GitHub Spec Kit workflow", "Kiro workflow", or invokes any SDD-style slash command. Single entry point for all SDD workflows.

The English summary is being prepared. Showing the original description.

Start an OpenSpec change for a feature, fix, or modification. Create its initial structure, show the workflow and current progress, and present the first planning document template for review before drafting any documents.

• Starting a feature change
• Setting up a bug fix plan
• Reviewing the first template in a chosen workflow

Continue an existing OpenSpec change by creating one planning artifact, such as a proposal or specification, per request. Read its dependencies and workflow instructions, complete missing files when needed, and report progress and newly available steps.

• Resuming an existing change plan
• Creating the next planning document
• Completing files missing after an interrupted draft

Manage prospects and clients for GEO services, which help sites prepare for AI search visibility. Keep contact details, audit history, notes, and monthly deal values in a local JSON file, and summarize sales stages and potential revenue.

• Register prospects and review their sales stages
• Keep audit history and dated interaction notes together
• Summarize won contracts and potential monthly revenue

Scaffold a Spec Kit (spec-driven development) project for GitHub Copilot by running `specify init --integration copilot --integration-options="--skills"`. USE FOR: starting a new spec-kit project, bootstrapping spec-driven development in an existing repo, installing spec-kit templates/scripts/commands for Copilot. DO NOT USE FOR: managing extensions/presets/bundles of an already-initialized project (use the speckit-extension / speckit-preset / speckit-bundle skills instead).

The English summary is being prepared. Showing the original description.

既存機能のSpec化。実装済みコードを分析して要件定義書を逆生成する。 spec-map.yml にコードとSpecの対応関係を記録する（コード変更なし）。 「ツイート機能のSpecを作って」「認証周りをドキュメント化して」「既存の○○機能を設計書にして」 「この機能の要件を整理して」「○○の仕様を分析して」などのリクエストで使用する。 既に動いているコードからドキュメントを起こすときに使う。新規機能にはdraft-specを使う。 コード変更後のドキュメント追従にはupdate-docsを使う。

The English summary is being prepared. Showing the original description.

Hard readiness gate before implementation begins — cross-checks the constitution, feature spec, plan, and tasks for consistency, traceability, and unresolved ambiguity. Returns PASS or FAIL with specific findings. Load when the spec-driven-development orchestrator routes /analyze, when the user asks to cross-check spec vs plan, audit traceability, verify spec readiness, gate-check before implementation, or says "is this spec implementation-ready", "trace requirements to tasks", "/analyze", "spec sanity check", "spec readiness gate", "spec consistency check". Output: docs/reviews/YYYY-MM-DD-<slug>-spec-crosscheck.md.

The English summary is being prepared. Showing the original description.

Implement pending tasks from an OpenSpec change, a planned set of development work. The skill reads relevant specifications and design files, makes focused code changes, and updates task completion as work progresses.

• Start implementing a planned change
• Resume partially completed implementation
• Work through pending tasks and track progress

Add and troubleshoot the json-render inspection panel in SolidJS applications. This skill covers panel setup for examining specifications, editing state, reviewing action and stream timelines, browsing component catalogs, and selecting page elements for inspection.

• Add an inspection panel to a SolidJS app
• Inspect JSON specifications and edit application state
• Review action and stream timelines

Build Rails 7+ applications with partial page updates, real-time connections, and background jobs. The skill implements Hotwire, Action Cable, and Sidekiq features, improves Active Record database queries, and writes RSpec tests.

• Adding partial page updates with Hotwire
• Building real-time features with Action Cable
• Moving slow tasks to Sidekiq jobs

Create, amend, or backprop bugs into SPEC.md at repo root. Sole mutator of the project spec. Triggers when the user asks to write a spec, start a new spec, distill a spec from existing code, add invariants, amend sections (§G, §C, §I, §V, §T, §B), or record a bug via backprop. Common phrasings: "write the spec for...", "new spec", "bug: ...", "amend §V.3", "distill spec from code", "spec this idea". Reads and follows FORMAT.md for the caveman encoding rules and pipe-table shape of §T and §B.

The English summary is being prepared. Showing the original description.

Generate structured software specifications for features, bug fixes, and products. Use when the user wants to create a spec, PRD, feature brief, requirements document, or when starting any new implementation that needs a specification first. Invoke via /spec-writer or when the user says "write a spec", "spec this out", "create a spec", "I need a spec for...", or describes a feature they want to build. Produces adaptive-complexity specs with Job Stories, Gherkin acceptance criteria, and three-tier boundaries. Output is a markdown file ready for agent execution or human review.

The English summary is being prepared. Showing the original description.

Fact-check finished OpenSpec documentation with a separate reviewer that checks commands, examples, and behavior against source files and actual output. Receive prioritized findings, suggested fixes, verification evidence, and a list of claims that remain unverified.

• Fact-check a documentation page before publication
• Verify commands and output in a specific section
• Recheck factual claims changed during a revision

Draft or rewrite an OpenSpec documentation page collaboratively. The skill records its purpose and structure inside the page, writes one section at a time as requested, then updates related references and removes the working plan.

• Shape a new documentation page together
• Rewrite a page from scratch
• Review and draft one section at a time

Manage OpenSpec releases by auditing merged changes and release records, checking release pull requests, and verifying publication. Support stable and beta releases, resume from the current GitHub state, and finish with polished release notes.

• Checking release readiness and missing change records
• Preparing a pull request for missing release records
• Resuming a release after human approval

Set up a new OpenSpec change for a feature, fix, or modification. Create its working directory, show the document sequence and current status, and present the first template so drafting can begin.

• Start a new feature change in OpenSpec
• Set up a change for a bug fix
• Start a change with a chosen workflow

Archive several OpenSpec changes together after reviewing their documents, task completion, and specification conflicts. The agent checks actual code to decide which specification updates to apply, asks for confirmation, and reports successes, skipped changes, and failures.

• Archiving several completed changes together
• Reviewing incomplete documents and tasks before archiving
• Resolving overlapping specifications using implementation evidence

Debug json-render interfaces with an inspector panel that shows screen specifications, editable runtime state, action history, and streamed updates. Select a rendered page element to locate its definition and investigate display or interaction problems.

• Investigate missing or incorrectly displayed elements
• Inspect and edit application state at runtime
• Review action results and errors

Create UI-SPEC.md, a document defining interface design decisions for a frontend phase. The skill coordinates UI research and specification checks, using a chosen phase or automatically selecting the next unplanned one.

• Preparing UI specifications for a frontend phase
• Researching UI before documenting design decisions
• Checking a UI specification after drafting it

Evaluate code against a product requirements document, scoring implementation and tests separately for each acceptance criterion. Produce an evidence-backed final grade, identify gaps, and compare implementations using a fixed checklist and scoring method.

• Checking whether a feature fulfills its requirements
• Comparing implementations of the same specification
• Auditing unit and end-to-end test coverage

When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).

The English summary is being prepared. Showing the original description.

This skill should be used when the user asks to "dev-screen-spec", "画面仕様を生成", "画面仕様を更新", "screen spec", "generate screen spec", "update screen spec", "画面仕様ドキュメント". ソースコードから画面仕様ドキュメントを自動生成・差分更新する。受け入れ条件から画面仕様を事前生成する from-plan モードも対応。

The English summary is being prepared. Showing the original description.

Intent-driven spec precipitation — state a constraint in natural language (加一条规范：禁止用 any / 记录架构约束：服务间走 gRPC / 质量规则：覆盖率≥80%) and the workflow infers the category and records a <spec-entry>. Spec = 项目约束规则（编码规范、架构约束、质量标准）；可复用知识文档走 /maestro-knowhow capture。Triggers on "maestro-spec add", "记录规范", "添加约束", "添加规则", "加一条规范", "spec add". Terminology：spec = project constraints/rules (<spec-entry>). Reusable knowledge documents use /maestro-knowhow capture. Learning discoveries from /maestro-learn use <learning-entry> tags in learnings.md (separate from spec entries).

The English summary is being prepared. Showing the original description.

Lightweight standalone design spec for AI coding agents: codebase scan → bounded clarify pass (3–5 questions, not a grill) → reviewed design doc written to docs/plans/ → independent scored review → stop. No task board, no build. Use when you want a spec to discuss, hand off, or review before committing to implementation. Chains into absolute-work when ready to build. Triggers on "absolute spec", "write a spec", "spec out this feature", "draft a design doc", "I want a spec to hand off / review, don't build it yet".

The English summary is being prepared. Showing the original description.