sdd-implement-spec

Automate feature spec implementation from branch creation to PR opening.

21|5|Updated May 21, 2026
One-click install
npx skills add https://github.com/jentic/jentic-api-scorecard --skill sdd-implement-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-implement-spec
Source: https://github.com/jentic/jentic-api-scorecard/tree/main/.claude/skills/sdd-implement-spec
Command: npx skills add https://github.com/jentic/jentic-api-scorecard --skill sdd-implement-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, github, spec-driven development, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the end-to-end implementation of feature specs in Spec-Driven Development (SDD) workflows, guiding users through the entire process from branch creation to PR opening.

Core Features & Use Cases

  • Branch Creation: Automatically creates a feature branch based on the spec.
  • Task Management: Manages tasks through their lifecycle, from planning to completion.
  • Verification: Ensures all tasks are completed and all checks pass before opening a PR.
  • Code Review: Facilitates a thorough code review process with multiple perspectives.
  • PR Opening: Opens a PR with a detailed description and all necessary information.
  • Use Case: A developer can use this Skill to implement a new feature, following the steps outlined in the spec, and ensure the implementation meets all requirements.

Quick Start

Run the sdd-implement-spec skill with the spec directory path as an argument, e.g., sdd-implement-spec specs/2026-05-21-gate-allowlist.

Frequently Asked Questions about sdd-implement-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate feature spec implementation in Spec-Driven Development?

Automate feature spec implementation by running a command with the spec directory path, which handles branch creation, task management, verification, code review, and PR opening. It guides the entire workflow end-to-end without manual intervention.

What is the best way to manage feature branches and PRs for spec-driven development?

Managing feature branches and PRs in spec-driven development is best handled by automating the lifecycle from branch creation to code review and PR opening. This ensures all spec tasks are completed and checks pass before submission.

Do I need Git and GitHub to automate spec-driven development workflows?

Yes, Git and GitHub are required dependencies to automate spec-driven development workflows. You also need an existing Spec-Driven Development setup to provide the feature specs for the automation process.

How does automated code review work for feature implementation specs?

Automated code review for feature specs facilitates a thorough review process from multiple perspectives before opening a PR. It verifies that all planned tasks are completed and all checks pass to ensure implementation meets requirements.

Can I use this automation to verify spec tasks before opening a pull request?

Yes, the automation verifies that all spec tasks are completed and all checks pass before opening a pull request. It manages tasks through their lifecycle from planning to completion to ensure strict spec compliance.

What are the limitations of automating feature implementation with spec-driven development?

The automation is limited to spec-driven development workflows and requires Git, GitHub, and a properly configured SDD setup. Without these dependencies or a defined spec directory, the automated branch and PR workflow cannot run.