One-click install
npx skills add https://github.com/masa-codehub/gemini_agent --skill drafting-specs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drafting-specs
Source: https://github.com/masa-codehub/gemini_agent/tree/main/.gemini/skills/drafting-specs
Command: npx skills add https://github.com/masa-codehub/gemini_agent --skill drafting-specs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Drafting-specs automates and unifies the process of turning planning notes and design decisions into concrete, test-ready specifications that serve as a contract for implementation and testing.

Core Features & Use Cases

  • Common Definitions enforcement: ensure terminology, data types, and error codes follow a shared standard.
  • Template-driven drafting: generate API/Data/Logic specs from planning artifacts.
  • Strict typing and edge-case coverage: specify concrete constraints and potential failures.
  • Self-audit, retrospective, and PR workflow: maintain quality and drive reviews.
  • Direct mapping to TDD artifacts: produce specs that can be transformed into tests.

Quick Start

Initiate drafting by activating the SMART goals step and then proceed through the drafting workflow to generate a complete specification.

Frequently Asked Questions about drafting-specs

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

FAQPage Schema
How do I convert planning notes into test-ready specifications for TDD?

A design doc specification requires strict typing, common definitions, comprehensive error handling, and edge-case coverage to become test-ready. Drafting these specs involves applying templates to planning artifacts to ensure terminology and data types follow a shared standard for implementation.

What is the best way to draft API and data specs from existing ADRs?

Yes, you can use template-driven drafting to generate API, data, and logic specs that align with test-driven development. By enforcing strict typing and thorough error handling within the specification, the resulting document serves as a direct contract that can be transformed into TDD artifacts.

How do I start the specification drafting workflow using planning artifacts?

During specification drafting, you handle edge-case coverage and error handling by explicitly defining concrete constraints and potential failures within the spec. The workflow enforces strict typing and thorough error condition mapping to ensure the final document is robust enough for production review and merging.

Does the specification drafting workflow include a self-audit and PR review process?

You should not use basic specification drafting when your project requires strict typing enforcement, common definitions standardization, and comprehensive edge-case coverage. Without template-driven workflows mapping planning artifacts to TDD-ready contracts, the resulting specs will lack the constraints needed for reliable refactoring and auditing.