Product Spec to Phased Engineering Implementation Plan Skill

Transform high-level product requirements and RFCs into dependency-ordered engineering tasks with explicit acceptance criteria, database migrations, and QA

---
name: spec-to-implementation
description: Transform high-level product requirements and RFCs into dependency-ordered engineering tasks with explicit acceptance criteria, database migrations, and QA verification steps. Use when working with Product Specs, Task Decomposition, Linear / Notion, Acceptance Criteria.
triggers:
  - spec to implementation
  - product specs
  - task decomposition
---

# Product Spec to Phased Engineering Implementation Plan Skill

## 1. When to Use This Skill
Load `skill-spec-to-implementation` whenever an engineering or operations task involves **Product Specs, Task Decomposition, Linear / Notion, Acceptance Criteria**. Specifically:
- Transform high-level product requirements and RFCs into dependency-ordered engineering tasks with explicit acceptance criteria, database migrations, and QA verification steps.
- Designing, reviewing, or debugging production configurations without guesswork or deprecated flags.
- Running deterministic pre-flight and post-execution verification checks before reporting completion.

## 2. Prerequisites & Required Environment
- **Target Stack:** Product Specs, Task Decomposition, Linear / Notion, Acceptance Criteria
- **Permissions:** Read-only inspection by default; ask for explicit confirmation before executing destructive mutations or production deployments.
- **Reference Repository:** `https://github.com/makenotion/notion-mcp-server`

## 3. Step-by-Step Execution Playbook
1. **Context & Configuration Discovery:**
   Inspect existing project manifests (`package.json`, `wrangler.jsonc`, schema files, or environment declarations) before proposing changes. Never overwrite existing bindings or credentials blindly.
2. **Deterministic Implementation:**
   Apply the canonical patterns for **Product Specs**:
   - Enforce strict schema/type validation at every external boundary.
   - Include explicit error handling, structured logging, and idempotency keys on all mutating calls.
   - Keep secrets in environment variables or secret stores—never hardcode tokens in source files.
3. **Verification & Regression Gate:**
   Run the verification commands below and inspect both exit codes and output payloads before marking the task complete.

## 4. Reference Commands & CLI Workflow
```bash
npx lightstate inspect skill-spec-to-implementation
```

## 5. Edge Cases & Anti-Hallucination Guardrails
- **Zero Unverified Claims:** Never claim a deployment, migration, or API call succeeded without inspecting the command output or HTTP status code.
- **Rollback Readiness:** Always record the previous state or migration version so changes can be reverted cleanly if downstream health checks fail.

Synthesized Engineering Blueprint & Setup Guide