القائمة
Author specwright-compatible specs with complete frontmatter, bounded scope, deterministic test plans, and acceptance criteria that map directly to deliverables.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Apply a safe branching model with branch naming, commit discipline, and merge/rebase flow. Use when starting implementation, preparing commits, syncing with main, and opening pull requests.
Create re-runnable infrastructure shell scripts for gcloud and bq that safely handle existing resources and produce deterministic outcomes across repeated executions.
Start a real local HTTP server process, send curl requests to live endpoints, and assert status codes and response content for quick smoke validation.
Bootstrap registrar-managed environments using registrar CLI, verify provisioned cloud resources, and capture reproducible evidence for dev, stage, and prod setup.
| name | specwright-spec-authoring |
| description | Author specwright-compatible specs with complete frontmatter, bounded scope, deterministic test plans, and acceptance criteria that map directly to deliverables. |
| metadata | {"author":"benthepsychologist","version":"1.0"} |
| allowed-tools | bash rg |
Use this skill when creating or revising a spec consumed by the Specwright execution flow.
Every spec starts with fully populated YAML frontmatter:
---
id: t000-00-example
tier: B
title: "Outcome-focused title"
owner: your-handle
goal: Clear one-sentence objective
validated: true
version: "2.0"
labels:
- specwright
epic: t000-epic
repo:
name: project-name
url: /workspace/project
working_branch: feat/example
depends_on: []
created: "2026-03-20T00:00:00Z"
updated: "2026-03-20T00:00:00Z"
---
Include these sections in order:
rg -n "^## (Objective|Problem|Deliverables|Test Plan|Acceptance Criteria|Boundary)" <spec-file>.md
If any required section is missing, revise before handoff.