{
  "id": "skl_09d53d481bca",
  "slug": "skill-spec-to-implementation",
  "asset_type": "skill",
  "name": "Product Spec to Phased Engineering Implementation Plan Skill",
  "tagline": "Transform high-level product requirements and RFCs into dependency-ordered engineering tasks with explicit acceptance criteria, database migrations, and QA",
  "description_md": "### Overview & Capability Scope\n**Product Spec to Phased Engineering Implementation Plan Skill** (`skill-spec-to-implementation`) is a verified, portable `SKILL.md` playbook curated with **@lennysan** for Grok Bot (`x.ai/bot/`), Claude Code (`~/.claude/skills/`), and Cursor (`.cursor/skills/`).\n\nTransform high-level product requirements and RFCs into dependency-ordered engineering tasks with explicit acceptance criteria, database migrations, and QA verification steps.\n\n### Required Stack & Tooling\n- **Primary Stack:** Product Specs, Task Decomposition, Linear / Notion, Acceptance Criteria\n- **Category:** `chief-of-staff`\n- **Source & Reference:** [https://github.com/makenotion/notion-mcp-server](https://github.com/makenotion/notion-mcp-server)\n\n### Quickstart Installation\nInstall this `SKILL.md` playbook directly into your agent workspace:\n```bash\nnpx lightstate install skill-spec-to-implementation\n```\nOr copy the complete `SKILL.md` specification below into `.cursor/skills/skill-spec-to-implementation/SKILL.md` or `~/.claude/skills/skill-spec-to-implementation/SKILL.md`.\n\n### Verification Commands\n```bash\nnpx lightstate inspect skill-spec-to-implementation\n```\n",
  "primary_category": "chief-of-staff",
  "categories_json": "[\"chief-of-staff\", \"skills\"]",
  "tags_json": "[\"product-specs\", \"task-decomposition\", \"linear-/-notion\", \"acceptance-criteria\", \"skill-md\", \"chief-of-staff\"]",
  "compatible_agents_json": "[\"grok-bot\", \"claude-code\", \"cursor\"]",
  "integrations_json": "[\"Product Specs\", \"Task Decomposition\", \"Linear / Notion\"]",
  "includes_json": "[]",
  "safety_level": "Read-Only / Ask-First",
  "safety_summary": "Verified capability blueprint by @lennysan.",
  "share_url": "",
  "deep_link_uri": "",
  "mcp_endpoint": "",
  "mcp_transport": "http",
  "install_command": "npx lightstate install skill-spec-to-implementation",
  "skill_markdown": "---\nname: spec-to-implementation\ndescription: 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.\ntriggers:\n  - spec to implementation\n  - product specs\n  - task decomposition\n---\n\n# Product Spec to Phased Engineering Implementation Plan Skill\n\n## 1. When to Use This Skill\nLoad `skill-spec-to-implementation` whenever an engineering or operations task involves **Product Specs, Task Decomposition, Linear / Notion, Acceptance Criteria**. Specifically:\n- Transform high-level product requirements and RFCs into dependency-ordered engineering tasks with explicit acceptance criteria, database migrations, and QA verification steps.\n- Designing, reviewing, or debugging production configurations without guesswork or deprecated flags.\n- Running deterministic pre-flight and post-execution verification checks before reporting completion.\n\n## 2. Prerequisites & Required Environment\n- **Target Stack:** Product Specs, Task Decomposition, Linear / Notion, Acceptance Criteria\n- **Permissions:** Read-only inspection by default; ask for explicit confirmation before executing destructive mutations or production deployments.\n- **Reference Repository:** `https://github.com/makenotion/notion-mcp-server`\n\n## 3. Step-by-Step Execution Playbook\n1. **Context & Configuration Discovery:**\n   Inspect existing project manifests (`package.json`, `wrangler.jsonc`, schema files, or environment declarations) before proposing changes. Never overwrite existing bindings or credentials blindly.\n2. **Deterministic Implementation:**\n   Apply the canonical patterns for **Product Specs**:\n   - Enforce strict schema/type validation at every external boundary.\n   - Include explicit error handling, structured logging, and idempotency keys on all mutating calls.\n   - Keep secrets in environment variables or secret stores—never hardcode tokens in source files.\n3. **Verification & Regression Gate:**\n   Run the verification commands below and inspect both exit codes and output payloads before marking the task complete.\n\n## 4. Reference Commands & CLI Workflow\n```bash\nnpx lightstate inspect skill-spec-to-implementation\n```\n\n## 5. Edge Cases & Anti-Hallucination Guardrails\n- **Zero Unverified Claims:** Never claim a deployment, migration, or API call succeeded without inspecting the command output or HTTP status code.\n- **Rollback Readiness:** Always record the previous state or migration version so changes can be reverted cleanly if downstream health checks fail.\n",
  "starter_prompt": "Load the Product Spec to Phased Engineering Implementation Plan Skill (skill-spec-to-implementation) playbook. First inspect our current configuration and codebase for Product Specs, Task Decomposition, Linear / Notion, Acceptance Criteria. Then propose a concrete, step-by-step implementation plan following the skill-spec-to-implementation guardrails, run the non-destructive verification commands (npx lightstate inspect skill-spec-to-implementation), and summarize any findings, risks, or required environment variables before making production changes.",
  "project_url": "https://github.com/makenotion/notion-mcp-server",
  "repo_url": "https://github.com/makenotion/notion-mcp-server",
  "creator_handle": "lennysan",
  "creator_name": "Lenny Rachitsky (@lennysan)",
  "creator_avatar_url": null,
  "creator_url": "https://x.com/lennysan",
  "creator_platform": "x",
  "creator_cal_url": null,
  "claimed_by_user_id": null,
  "scouted_by_handle": null,
  "source_url": "https://github.com/makenotion/notion-mcp-server",
  "source_tweet_id": null,
  "source_origin": "certified_builder",
  "source_posted_at": null,
  "x_likes": 268,
  "x_bookmarks": 624,
  "x_retweets": 156,
  "x_views": 3752,
  "human_upvotes": 268,
  "human_installs": 268,
  "bot_pulls": 624,
  "pulse_score": 92,
  "gravity_rank_score": 2238,
  "is_featured": 0,
  "is_verified": 1,
  "is_sponsored": 0,
  "sponsor_tier": "free",
  "sponsor_label": "",
  "sponsor_cta_url": "",
  "sponsor_expires_at": null,
  "commercial_intent_score": 0,
  "status": "active",
  "created_at": "2026-10-24T20:00:00Z",
  "updated_at": "2026-10-24T20:00:00Z",
  "verified_at": null,
  "primitive": "skill",
  "title": "Product Spec to Phased Engineering Implementation Plan Skill",
  "description": "Transform high-level product requirements and RFCs into dependency-ordered engineering tasks with explicit acceptance criteria, database migrations, and QA",
  "category": "chief-of-staff",
  "tags": "[\"product-specs\", \"task-decomposition\", \"linear-/-notion\", \"acceptance-criteria\", \"skill-md\", \"chief-of-staff\"]",
  "agent_compatibility": "[\"grok-bot\", \"claude-code\", \"cursor\"]",
  "author_handle": "lennysan",
  "author_name": "Lenny Rachitsky (@lennysan)",
  "author_avatar": null,
  "source_tweet_url": "https://github.com/makenotion/notion-mcp-server",
  "github_url": "https://github.com/makenotion/notion-mcp-server",
  "external_url": "https://github.com/makenotion/notion-mcp-server",
  "upvotes_count": 268,
  "installs_count": 268
}