ワンクリックでManusで任意のスキルを実行

speckit-specify

スター5

フォーク4

更新日2026年5月14日 19:22

Generate a spec.md file under specs/<feature>/ describing a new pickup-points-modal feature in Business Context, Architectural Decisions, and Technical Contract sections.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

vtex

vtex/pickup-points-modal

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

関連職種SOC

SOC 職業分類に基づく

コンピュータシステムアナリストコンピュータ・数学職·SOC 15-1211

SKILL.md

readonly

このリポジトリの他の Skills

同じリポジトリ

implementing

vtex/pickup-points-modal

Implement an approved spec end-to-end in the pickup-points-modal repo — branch, code, tests, lint, typecheck, build, commit, and open a PR following Conventional Commits and the project constitution.

2026-05-145

specification

vtex/pickup-points-modal

Generate an SDD (Spec Driven Development) document for a new feature in the pickup-points-modal, covering Business Context, Architectural Decisions, and Technical Contract before any code is written.

2026-05-145

speckit-analyze

vtex/pickup-points-modal

Audit consistency between spec.md, plan.md, tasks.md, and the actual code in the pickup-points-modal — flagging drift, missing tasks, or out-of-spec changes before PR review.

2026-05-145

speckit-checklist

vtex/pickup-points-modal

Generate a per-feature validation checklist (pre-merge gates, manual QA steps, rollback plan) for a pickup-points-modal feature, tailored to the spec and constitution principles.

2026-05-145

speckit-clarify

vtex/pickup-points-modal

Interactively clarify ambiguous requirements in a spec.md before planning — generates targeted questions for the requester to resolve TBDs in the pickup-points-modal feature spec.

2026-05-145

speckit-constitution

vtex/pickup-points-modal

Create or amend the project constitution in .specify/memory/constitution.md, capturing binding principles, governance, and ratification metadata for the pickup-points-modal.

2026-05-145

name	speckit-specify
description	Generate a spec.md file under specs/<feature>/ describing a new pickup-points-modal feature in Business Context, Architectural Decisions, and Technical Contract sections.
type	skill

speckit-specify

Use to turn a natural-language description into a structured spec.md. It is the first step of the Full Golden Path (SDD).

When to use

New feature requested via Jira/Slack.
The user says "spec this feature: ..." or "/speckit-specify ...".

Flow

Create the specs/<feature-slug>/ folder.
Run .specify/scripts/bash/create-new-feature.sh <slug> if available; otherwise create the folder manually.
Fill spec.md using the template at .specify/templates/spec-template.md.
Mark unresolved fields as TBD — do not invent answers.
Present the draft to the user before starting speckit-plan.

Minimum inputs to avoid mass-TBD

Who requested it (Jira/PM/stakeholder)?
What user-facing problem are we solving?
Which files/components are likely affected?

Output

specs/<slug>/spec.md with the sections:

Business Context
Architectural Decisions
Technical Contract (props, fixtures, i18n, tests, acceptance)

Important

/specs is in .gitignore — it is a local-only directory. Do not commit specs into this public repo. To archive, move them to the internal Confluence space.