بنقرة واحدة
implement-it
Begins implementing a task following an implementation plan.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Begins implementing a task following an implementation plan.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Provides a brief explanation of the code attached, including key components, notable patterns, and a code walkthrough.
Provides a code review of the attached code changes.
Provides a brief explanation of the code attached, including key components, notable patterns, and a code walkthrough. Use when the user asks to explain, understand, or walk through code.
Provides a code review of the attached code changes. Use when the user asks for a code review, PR review, or feedback on code changes.
Begins implementing a task following an implementation plan. Use when the user asks to implement a feature, fix a bug, or build something based on an existing plan or task file.
Creates an implementation plan markdown file from a task description. Use when the user describes a new feature or task and wants a structured plan before implementation begins.
| name | implement-it |
| description | Begins implementing a task following an implementation plan. |
This rule guides the implementation of tasks in a methodical, step-by-step approach with user verification at each stage.
Create Implementation Plan: First, create a {task-name-}steps.md file that breaks down the task into clear, manageable steps.
One Step at a Time: Implement only one step at a time, focusing on quality and completeness for each individual component.
User Verification: After completing each step, check with the user to ensure it was implemented correctly before proceeding.
Iterative Refinement: Based on user feedback, refine the implementation as needed before moving to the next step.
Documentation: Keep the steps.md file updated with progress, changes, and completion status.
When checking with the user after each step:
This approach ensures high-quality implementation with continuous user alignment throughout the development process.