spec-bundle

星标0

分支0

更新时间2026年7月18日 20:35

Build an implementation-ready spec bundle when a plain PRD is no longer enough: minimum useful contracts, schema, test plan, blueprint, gates, ADRs, boundaries, and GitHub-ready task breakdown. Use when ambiguity or architecture risk would otherwise slow execution.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

kiku-jw

kiku-jw/codex-skills

打开 GitHub 仓库查看创作者相关仓库

下载

Spec Bundle

Metadata

Trigger when: a plain PRD is too soft and the implementation needs contracts, schema, test planning, or architecture boundaries to move safely.
Do not use when: a short brief is enough and extra artifacts would be paperwork theater.

Skill Purpose

Create only the spec artifacts that materially reduce ambiguity, rework, or review pain so implementation can start from clear contracts and gates instead of vibes.

Instructions

Decide the smallest honest bundle first: core bundle, architecture pack, and optional ADRs only when the risk profile justifies them. If scaffolding helps, use /Users/nick/.codex/skills/spec-bundle/scripts/init_bundle.py with the appropriate flags. Use /Users/nick/.codex/skills/spec-bundle/references/bundle-shape.md only when you need the exact shape.
Fill only the artifacts that change implementation quality: prd.md, contracts.md, schema.sql, test-plan.md, epics.md, and only add blueprint.md, gate-matrix.md, or adr/ when architecture risk, gating, or irreversible decisions make them worth keeping.
Validate traceability and consistency. Contracts must point to consuming tasks, gates must name blocking evidence, and bundle artifacts must be updated together when requirements or architecture move.

Non-Negotiable Acceptance Criteria

One source of truth per concern: scope, contracts, DB shape, validation, and task breakdown stay separated.
Architecture pack artifacts exist only when the risk is real.
Local/cloud boundaries are explicit when they matter.
If an artifact would be fake theater, leave it out or mark it intentionally deferred.

Output

The created or updated bundle artifacts on disk.
A short note on bundle size: core only, architecture pack, or architecture pack plus ADRs.
Any unresolved gate or assumption that still blocks clean implementation.
Next skill options (only if needed): $justdoit — convert the bundle into a live execution plan; $adr-log — capture an irreversible architectural choice; $issue-control-loop — move the bundle into a durable GitHub issue workflow; $agx-orchestrator — dispatch bounded execution after the bundle is stable.

同仓库更多 Skills

同仓库

github-seo

kiku-jw/codex-skills

Audit and improve a public GitHub repository's discoverability and any linked canonical site without confusing repository presentation with website SEO. Use for repository SEO, GitHub discoverability, topics/homepage/README optimization, GitHub Pages SEO, AEO, or agent-friendly public documentation.

2026-07-230

spreadsheet

kiku-jw/codex-skills

Create, edit, analyze, or format spreadsheets (`.xlsx`, `.csv`, `.tsv`) with `openpyxl` and `pandas`, especially when formulas, references, and formatting must survive the change. Use when spreadsheet integrity matters more than ad hoc CSV hacking.

2026-07-180

spreadsheet-tabular-analysis

kiku-jw/codex-skills

Analyze and reshape spreadsheet, CSV, or TSV data with `pandas` and stable output files. Use when the job is aggregation, filtering, joins, metrics, or tabular transformations rather than workbook-style editing.

2026-07-180

spreadsheet-xlsx-edit

kiku-jw/codex-skills

Create or edit `.xlsx` workbooks while preserving formulas, references, formatting, and layout. Use when workbook integrity matters more than raw data analysis.

2026-07-180

transcribe-basic

kiku-jw/codex-skills

Produce a fast plain-text transcript with the bundled CLI using the light transcription model. Use when speaker diarization is not needed.

2026-07-180

transcribe-diarize

kiku-jw/codex-skills

Produce a speaker-aware transcript with diarization and optional known-speaker hints using the bundled CLI. Use when the user explicitly needs speaker labels.

2026-07-180

name	spec-bundle
description	Build an implementation-ready spec bundle when a plain PRD is no longer enough: minimum useful contracts, schema, test plan, blueprint, gates, ADRs, boundaries, and GitHub-ready task breakdown. Use when ambiguity or architecture risk would otherwise slow execution.

Spec Bundle

Metadata

Trigger when: a plain PRD is too soft and the implementation needs contracts, schema, test planning, or architecture boundaries to move safely.
Do not use when: a short brief is enough and extra artifacts would be paperwork theater.

Skill Purpose

Create only the spec artifacts that materially reduce ambiguity, rework, or review pain so implementation can start from clear contracts and gates instead of vibes.

Instructions

Decide the smallest honest bundle first: core bundle, architecture pack, and optional ADRs only when the risk profile justifies them. If scaffolding helps, use /Users/nick/.codex/skills/spec-bundle/scripts/init_bundle.py with the appropriate flags. Use /Users/nick/.codex/skills/spec-bundle/references/bundle-shape.md only when you need the exact shape.
Fill only the artifacts that change implementation quality: prd.md, contracts.md, schema.sql, test-plan.md, epics.md, and only add blueprint.md, gate-matrix.md, or adr/ when architecture risk, gating, or irreversible decisions make them worth keeping.
Validate traceability and consistency. Contracts must point to consuming tasks, gates must name blocking evidence, and bundle artifacts must be updated together when requirements or architecture move.

Non-Negotiable Acceptance Criteria

One source of truth per concern: scope, contracts, DB shape, validation, and task breakdown stay separated.
Architecture pack artifacts exist only when the risk is real.
Local/cloud boundaries are explicit when they matter.
If an artifact would be fake theater, leave it out or mark it intentionally deferred.

Output

The created or updated bundle artifacts on disk.
A short note on bundle size: core only, architecture pack, or architecture pack plus ADRs.
Any unresolved gate or assumption that still blocks clean implementation.
Next skill options (only if needed): $justdoit — convert the bundle into a live execution plan; $adr-log — capture an irreversible architectural choice; $issue-control-loop — move the bundle into a durable GitHub issue workflow; $agx-orchestrator — dispatch bounded execution after the bundle is stable.