skills.rest
EEstevanell
EEstevanellCOMMUNITY
Explore all skills by this author →
GitHub

implement-issue-execplan

Implement issue-driven changes by executing an ExecPlan aligned with AGENTS.md and PLANS.md.

2|Updated Feb 5, 2026
Search Tags:#automation#traceability#implement#AGENTS.md#PLANS.md#execplan#issue-card
One-click install
npx skills add https://github.com/EEstevanell/codex-planning-kit --skill implement-issue-execplan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-issue-execplan
Source: https://github.com/EEstevanell/codex-planning-kit/tree/main/.codex/skills/implement-issue-execplan
Command: npx skills add https://github.com/EEstevanell/codex-planning-kit --skill implement-issue-execplan

SYSTEM DOCUMENTATION & REQUIREMENTS

Implement a feature or fix by executing an issue card plus ExecPlan in this repo. Use when Codex is asked to implement work that must align with AGENTS.md and PLANS.md, keep the ExecPlan updated, and treat any referenced repo docs as authoritative. Requires ISSUE_PATH and EXECPLAN_PATH.

Frequently Asked Questions about implement-issue-execplan

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

FAQPage Schema
How do I automate issue-driven implementation while keeping AGENTS.md and PLANS.md aligned?▼

Automate issue-driven implementation by executing an issue card alongside an ExecPlan, which validates changes against PLANS.md and treats referenced repo docs as authoritative before coding begins. This ensures full traceability and adherence to project documentation.

What is an ExecPlan and when do I need it for software engineering tasks?▼

An ExecPlan is a structured execution plan used alongside an issue card to drive feature implementation. You need it when changes must strictly align with AGENTS.md and PLANS.md, requiring validation and traceability throughout the coding process.

How to implement a feature fix from an issue card using an ExecPlan?▼

Provide the ISSUE_PATH and EXECPLAN_PATH, then the system validates the ExecPlan against PLANS.md, reads authoritative repo docs, and implements the changes while keeping the ExecPlan updated throughout the execution.

Do I need an issue card and ExecPlan path to use this automation approach?▼

Yes, you must provide both ISSUE_PATH and EXECPLAN_PATH. The automation requires these inputs to validate the plan against PLANS.md and execute the issue-driven changes with proper traceability.

Does this approach validate code changes against existing project documentation?▼

Yes, it validates the ExecPlan against PLANS.md and reads referenced repository docs as authoritative before coding. This ensures all changes align with existing project documentation and maintain traceability.

Can I use issue card automation for tasks that require strict documentation traceability?▼

Yes, this automation is designed for software engineering tasks that require traceability, validation, and adherence to project documentation. It keeps the ExecPlan updated and treats referenced repo docs as authoritative throughout execution.

Related Skills

Explore More Software Engineering Skills→
EEstevanellEEstevanell
2

align-issue-card

Align issue cards with ExecPlans against AGENTS.md and PLANS.md standards.

Community
Intermediate
EEstevanellEEstevanell
2

review-issue-implementation

Validate code diffs against issue cards and ExecPlans using AGENTS.md and PLANS.md.

Community
Intermediate
rilicalrilical

bootstrap-repo

Automate repo-wide scaffolding updates across AGENTS.md and PLANS.md.

Community
Intermediate
BrennonTWilliamsBrennonTWilliams
7

ll-verify-issues

Verify issue documentation claims against current source code.

Community
Intermediate