software-development

Convert GitHub issue specifications into modular, test-driven code implementations.

1|Updated Oct 21, 2025
One-click install
npx skills add https://github.com/bryonjacob/aug --skill software-development-bryonjacob
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-development
Source: https://github.com/bryonjacob/aug/tree/main/aug-dev/skills/software-development
Command: npx skills add https://github.com/bryonjacob/aug --skill software-development-bryonjacob

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates GitHub issue specifications into structured, test-driven code modules, reducing manual translation and ensuring verifiable progress.

Core Features & Use Cases

  • Chunked Implementation: Breaks work into small, testable increments aligned with issue guidance.
  • Automated Testing: Enforces unit tests after every chunk and validates quality gates via just checks.
  • Public Interface & Documentation: Produces a clean module structure with contracts, tests, and documentation.

Quick Start

Start by creating the GitHub issue spec, scaffold the module with init.py, core.py, models.py, and tests/, implement the first chunk, add unit tests, and run the quality gates until all tests pass.

Frequently Asked Questions about software-development

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

FAQPage Schema
How do I automate turning GitHub issues into tested code modules?

To automate turning GitHub issues into tested code, this Skill translates issue specifications into structured, test-driven modules, breaking work into small chunks with unit tests and quality gates after each increment.

What is the best way to enforce unit tests after every code chunk from an issue?

Enforcing unit tests after every code chunk is handled by validating quality gates via just, ensuring each increment aligned with your GitHub issue guidance is tested before moving forward.

How do I structure a module for issue-driven software delivery?

To structure a module for issue-driven software delivery, scaffold it with __init__.py, core.py, models.py, and a tests/ directory, implementing the first chunk and adding unit tests to maintain a clear public interface.

Does this approach work with justfile for quality gates?

Yes, this approach works with justfile by using it to run quality gates, validating that unit tests pass after each chunk of implementation before progressing to the next issue requirement.

Can I use chunked implementation for existing GitHub issue specs?

You can use chunked implementation for existing GitHub issue specs by applying this workflow to break down defined tasks into modular, testable increments with automated tests and documentation.