implement

Route SMG feature implementation through subsystem-specific recipes with step verification.

11|2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/lightseekorg/smg-dev-guide --skill implement-lightseekorg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/lightseekorg/smg-dev-guide/tree/main/skills/implement
Command: npx skills add https://github.com/lightseekorg/smg-dev-guide --skill implement-lightseekorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Implement skill guides developers to implement features, fix bugs, or modify behavior in the SMG repository by routing work through subsystem-specific recipes and enforcing a strict, step-by-step workflow.

Core Features & Use Cases

  • Routes to the relevant subsystem recipe and loads it before writing code
  • Creates a task for each step in the loaded recipe and enforces execution order with verification
  • Bridges coding activity to the project’s contribute workflow via a final quality gate

Quick Start

Identify the subsystem, load its recipe, and create a task for each step before coding.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I implement a feature step by step in the SMG repository?

Step-by-step feature implementation requires loading the relevant subsystem recipe first. This skill coordinates the process by generating per-step tasks from the recipe and enforcing strict execution order with verification before proceeding.

What is a subsystem recipe for feature implementation?

A subsystem recipe is a guided workflow that defines the exact steps needed to modify specific parts of the SMG repository. The implement skill loads the correct recipe based on detected signals like CLI flags or routing changes before any code is written.

Can I fix bugs and modify behavior using a task-management workflow?

Yes, you can fix bugs and modify behavior using this task-management workflow. The skill applies its step-by-step execution process to SMG tasks, generating individual tasks for each recipe step and verifying progress before moving forward.

How does verification work before proceeding to the next implementation task?

Verification works by enforcing strict execution checks after each generated task in the loaded recipe. The skill ensures progress is verified at every step before allowing the workflow to proceed to the next coding task or the final quality gate.

Do I need to detect signals like CLI flags before creating an implementation plan?

Yes, detecting signals like CLI flags, config, or routing changes is necessary before creating an implementation plan. The skill uses these detected signals to route your work to the correct subsystem recipe and generate accurate per-step tasks.

What happens after completing the step-by-step feature implementation?

After completing step-by-step feature implementation, the workflow chains to the smg:contribute quality gate. This final quality gate bridges your coding activity to the project's contribution workflow to ensure standards are met.