skills.rest
cody-hutson
cody-hutsonCOMMUNITY
Explore all skills by this author →
GitHub

pmo-software-engineer

Convert approved implementation plans into code changes and generate verified PRs.

Updated Jun 5, 2026
Search Tags:#software engineering#verification#plan execution#change management#PR generation
One-click install
npx skills add https://github.com/cody-hutson/pmo-platform --skill pmo-software-engineer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pmo-software-engineer
Source: https://github.com/cody-hutson/pmo-platform/tree/main/release/skills/pmo-software-engineer
Command: npx skills add https://github.com/cody-hutson/pmo-platform --skill pmo-software-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires implementation-planner, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The pmo-software-engineer Skill resolves the need for efficient and precise execution of Stage-6 Engineering tasks, ensuring that approved plans are converted into executed changes and verified Pull Requests (PRs).

Core Features & Use Cases

  • Plan Execution: Turns approved implementation plans into executed code changes.
  • Verification: Performs checks against compliance and functional correctness.
  • PR Generation: Produces PRs with detailed version-log entries for actual changes made.
  • Use Case: Ideal for Software Engineers who need to execute a plan with a high degree of precision, ensuring that changes are correctly applied and tested before merging into the codebase.

Quick Start

Execute the plan for 'issue-123' by running 'pmo-software-engineer issue-123'.

Frequently Asked Questions about pmo-software-engineer

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

FAQPage Schema
How do I convert an approved implementation plan into executed code changes and a pull request?▼

To convert an approved implementation plan into executed code changes and a pull request, you can use a plan execution workflow that applies the changes, verifies functional correctness, and generates a PR with detailed version-log entries.

What is Stage-6 Engineering in software development?▼

Stage-6 Engineering is the precise execution phase of software development where approved implementation plans are turned into actual code changes, verified for compliance, and packaged into pull requests for merging into the codebase.

How do I verify compliance and functional correctness before generating a pull request?▼

You verify compliance and functional correctness by running QA checks against the executed code changes immediately after applying the implementation plan, ensuring the modifications meet all requirements before PR generation.

Do I need an implementation planner to execute code changes?▼

Yes, an implementation planner is required to generate the approved implementation plans that serve as the input, which the execution process then uses to accurately apply the code changes and generate the final pull request.

What's the best way to automate PR generation with detailed version logs?▼

The best way to automate PR generation with detailed version logs is to execute the plan using a dedicated workflow that automatically produces PRs containing precise version-log entries for all actual changes made during execution.

Related Skills

Explore More Software Engineering Skills→
dynatrace-ossdynatrace-oss
10

pr-reviewer

Review pull request diffs and comments to generate a structured review brief.

Official
Intermediate
muratmirgunmuratmirgun
8

go-code-review

Review Go diffs with severity-labeled findings and rule citations.

Community
Advanced
1J6K211J6K21

using-agent-skills

Discover and apply the appropriate engineering skill for a given development task.

Community
Intermediate
eykdeykd

quality-review

Review GitHub pull requests for correctness, style, test coverage, and standards.

Community
Advanced