pg

Implement software features from specifications into tested, maintainable code.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/codetail-ai/skillwright --skill pg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pg
Source: https://github.com/codetail-ai/skillwright/tree/main/roles/pg-agent
Command: npx skills add https://github.com/codetail-ai/skillwright --skill pg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a design, ticket, or clear specification into maintainable implementation work, helping engineers move from requirements to production-ready code without guessing at behavior.

Core Features & Use Cases

  • Reads the spec first and identifies the exact code paths that need to change.
  • Matches the repository’s existing conventions for structure, naming, error handling, logging, and testing.
  • Writes the implementation and unit tests together, then validates the result with review, linting, and type checks.
  • Use it when you need a feature built from a design doc, a bug fixed with regression coverage, or a small code change completed in a PR-ready form.

Quick Start

Tell the Skill what feature you want implemented and provide the spec or design doc so it can plan the change and write the code and tests.

Frequently Asked Questions about pg

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

FAQPage Schema
How do I turn a design spec into tested and maintainable code?

To turn a design spec into tested code, feed the specification to the Skill so it can read the codebase, match existing conventions, write the implementation with unit tests, and validate the result with lint and type checks.

What is the best way to implement a feature from a design doc while matching repository conventions?

The best way to implement a feature from a design doc is using an automation tool that reads your spec, identifies exact code paths to change, and matches repository conventions for naming, error handling, and testing.

Can I generate unit tests and implementation together from a ticket specification?

Yes, you can generate unit tests and implementation together by providing a clear ticket specification, which allows the tool to write both simultaneously and then validate the behavior with self-review checks.

Do I need a complete specification to get PR-ready code changes?

Yes, you need a complete specification to get PR-ready code changes because the implementation process depends on reading clear specs to plan the change, write tests, and verify behavior accurately.

How does spec to code implementation handle lint and type verification?

Spec to code implementation handles lint and type verification by running self-review checks after writing the code and unit tests, ensuring the delivered changes pass linting, type checks, and behavior validation.

When should I not use automated code implementation from specifications?

You should not use automated code implementation from specifications when you lack a clear spec or design doc, as the process requires reading existing specifications to identify code paths and deliver maintainable changes.