implement

Implement approved plans into focused code and documentation changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Jeqqe/jersal-project-template --skill implement-jeqqe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/Jeqqe/jersal-project-template/tree/main/.pi/skills/implement
Command: npx skills add https://github.com/Jeqqe/jersal-project-template --skill implement-jeqqe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you convert an approved plan or clear task into implementation-ready code and documentation, without drifting scope or jumping straight into PR creation too early.

Core Features & Use Cases

  • Scope-to-work conversion: Translates an approved plan or specific issue/task into focused workspace edits.
  • Branch-safe execution: Guides you to implement on the appropriate branch and manage local changes safely.
  • Targeted validation and handoff: Encourages running the right checks for the changed area and producing an actionable implementation summary for review.

Quick Start

Run /skill:implement with the relevant issue number or task description to make the approved plan’s changes in your workspace and prepare a validation-backed handoff to review.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I turn an approved plan into focused code changes without expanding scope?

To turn an approved plan into focused code changes, translate issue-scoped tasks into targeted workspace edits while gathering minimal read-only context. This prevents scope drift by ensuring only the necessary code and documentation updates are made before moving to the review phase.

What is the best way to prepare code changes for a review handoff?

The best way to prepare code changes for a review handoff is to run targeted validations for the changed area and output a structured implementation summary. This summary details file-level changes and check results, providing reviewers with actionable context.

How do I fix review findings without introducing unrelated code modifications?

Fixing review findings without introducing unrelated modifications requires applying changes strictly within the issue scope. By managing local changes safely and confirming planning gates, you can resolve feedback while maintaining the original implementation boundaries.

Does this implementation workflow require a fully approved plan before coding starts?

Yes, this implementation workflow requires a fully approved plan before coding starts. It confirms planning gates when needed to ensure the task is clearly defined, preventing premature code generation and keeping the development effort focused on validated objectives.

Can I run targeted validations for a changed code area before creating a pull request?

Yes, you can run targeted validations for a changed code area before creating a pull request. The workflow encourages executing the right checks for the modified region and producing an implementation summary to ensure the handoff is validation-backed.

How do I manage branch-safe execution when implementing new features?

Managing branch-safe execution when implementing features involves guiding the process to work on the appropriate branch and handling local changes safely. This ensures the workspace edits remain isolated and structured until the validation-backed handoff is ready.