feature

Implement new software features from issue tracker entries into pull requests.

2|1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Vekta/PolyForge --skill feature-vekta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/Vekta/PolyForge/tree/main/skills/feature
Command: npx skills add https://github.com/Vekta/PolyForge --skill feature-vekta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of implementing new features directly from issue trackers, streamlining the development lifecycle from planning to pull requests.

Core Features & Use Cases

  • Automated Branching: Creates feature branches based on issue numbers and descriptions.
  • Iterative Implementation: Builds features layer by layer (Schema, Core, API, Tests, Docs), with options for sub-agent delegation.
  • Commit Management: Cleans up commit history for logical grouping before PR creation.
  • Use Case: When a new user story is created in GitHub, this Skill can automatically branch, implement the required code, run tests, and open a pull request for review.

Quick Start

Use the feature skill to implement the requirements from issue number 42.

Frequently Asked Questions about feature

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

FAQPage Schema
How do I automate feature implementation from issue tracking entries?

Automating feature implementation from issue tracking entries involves scanning your codebase for existing patterns, planning steps, creating feature branches, and developing code iteratively across schema, core, API, tests, and documentation layers before generating a pull request.

What is the best way to generate a pull request from a GitHub issue automatically?

Generating a pull request from a GitHub issue automatically requires creating a feature branch based on the issue number, implementing code iteratively, cleaning up commit history, and opening the pull request for review.

How does iterative development work when automating feature branches?

Iterative development during automated feature branching builds the new software feature layer by layer across schema, core, API, tests, and documentation, with options for sub-agent delegation to manage the implementation steps.

Does automated feature implementation manage git commit history before creating a pull request?

Automated feature implementation manages git commit history by cleaning up and logically grouping commits before pull request creation, ensuring the development lifecycle from planning to review is streamlined.

Can I use automated feature development to scan my existing codebase for patterns?

You can use automated feature development to scan your existing project codebase for established patterns, which informs the planning of implementation steps and ensures new code adheres to current architectural conventions.