Agent skill
implement
Execute a GitHub issue or spec end-to-end. Inline two-layer plan, code, verify.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/implement-lightforgelabsstudio-aide
SKILL.md
Implement
Execute a GitHub issue or spec. Read AGENTS.md if not in context.
Inputs
Issue number (gh issue view <n>) or pasted spec text. If no spec exists, use /design first.
Review-aware
Before starting: check if <issue-slug>.findings.md exists. If it does, read it and incorporate findings before proceeding.
If CI or a test is red, compare against main and inspect the full PR commit range before classifying the failure. If the failure appears anywhere in the PR range, treat it as branch-owned and fix it in this PR.
Before touching code
- Confirm: Goal / Success Criteria / Scope. Ask if missing or ambiguous.
- State which files you plan to read before reading them.
- Layer 1 — filter applicable constraints from AGENTS.md (≤8 bullets): which invariants, authoritative systems, and boundaries govern this task.
- Layer 2 — ordered steps with exit criteria:
[Step] → Exit: [how to verify]. State this plan explicitly before writing any code.
Implementation
- Follow patterns in AGENTS.md. Load Tier 2 refs only when the task requires them.
- Do not modify existing tests without explicit approval.
- Keep diffs small and single-purpose.
After coding
- Verify each Layer 2 exit criterion is met.
- Run:
{{RUN_ALL_TESTS_COMMAND}}and{{LINT_COMMAND}} - Report: what changed, which criteria are satisfied, any gaps.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?