Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

speckit-specify

Estrelas456

Forks19

Atualizado29 de março de 2026 às 17:06

Use when working in this Spec Kit repository and the user wants to create or update a feature specification from a natural-language request, including the feature spec and its requirements checklist artifacts.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

zolotukhin

zolotukhin/zinc

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Outras ocupações de informáticaInformática e Matemática·SOC 15-1299

SKILL.md

readonly

name	speckit-specify
description	Use when working in this Spec Kit repository and the user wants to create or update a feature specification from a natural-language request, including the feature spec and its requirements checklist artifacts.

Speckit Specify

Use this skill for the Spec Kit specify phase.

Read ../../../.claude/commands/speckit.specify.md and treat it as the authoritative workflow.
Treat the current user request as the $ARGUMENTS referenced there. When the source workflow talks about text entered after /speckit.specify, it means the current user prompt.
Translate slash-command references to Codex skill names such as speckit-specify, speckit-clarify, speckit-plan, speckit-tasks, speckit-analyze, speckit-implement, speckit-checklist, speckit-constitution, and speckit-taskstoissues.
Use the repo-local .specify/scripts/bash/*.sh and .specify/templates/*.md files the workflow calls for.
Keep the spec workflow source-of-truth in the existing Spec Kit templates and command doc. Do not create parallel Codex prompt files.
Do not create Codex custom prompt files. Codex support in this repo is skill-based.

Mais deste repositório

mesmo repositório

zig-docgen

zolotukhin/zinc

Use when adding or editing Zig code in ZINC and you want it to remain compatible with the auto-generated Zig API docs. Covers the comment format, supported tags, parser limitations, section naming, and validation steps needed for reliable HTML, JSON, text, and llms exports.

2026-05-25456

speckit-analyze

zolotukhin/zinc

Use when working in this Spec Kit repository and the user wants a read-only consistency and coverage analysis across the active feature's spec.md, plan.md, and tasks.md before implementation.

2026-03-29456

speckit-checklist

zolotukhin/zinc

Use when working in this Spec Kit repository and the user wants a requirements-quality checklist for the active feature, generated from the current spec, plan, and tasks artifacts.

2026-03-29456

speckit-clarify

zolotukhin/zinc

Use when working in this Spec Kit repository and the user wants to resolve ambiguity in the active feature spec by asking targeted clarification questions and writing the accepted answers back into spec.md.

2026-03-29456

speckit-constitution

zolotukhin/zinc

Use when working in this Spec Kit repository and the user wants to create or amend the project constitution in .specify/memory/constitution.md and keep dependent templates aligned.

2026-03-29456

speckit-implement

zolotukhin/zinc

Use when working in this Spec Kit repository and the user wants to execute the active tasks.md plan, respecting checklist gates, task dependencies, and phase-by-phase implementation.

2026-03-29456

name	speckit-specify
description	Use when working in this Spec Kit repository and the user wants to create or update a feature specification from a natural-language request, including the feature spec and its requirements checklist artifacts.

Speckit Specify

Use this skill for the Spec Kit specify phase.

Read ../../../.claude/commands/speckit.specify.md and treat it as the authoritative workflow.
Treat the current user request as the $ARGUMENTS referenced there. When the source workflow talks about text entered after /speckit.specify, it means the current user prompt.
Translate slash-command references to Codex skill names such as speckit-specify, speckit-clarify, speckit-plan, speckit-tasks, speckit-analyze, speckit-implement, speckit-checklist, speckit-constitution, and speckit-taskstoissues.
Use the repo-local .specify/scripts/bash/*.sh and .specify/templates/*.md files the workflow calls for.
Keep the spec workflow source-of-truth in the existing Spec Kit templates and command doc. Do not create parallel Codex prompt files.
Do not create Codex custom prompt files. Codex support in this repo is skill-based.