implement

Implements Linear issues through an 8-step protocol with spec gates and post-implementation validation.

2|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Vibecoder79/jarvis --skill implement-vibecoder79
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/Vibecoder79/jarvis/tree/main/.claude/skills/implement
Command: npx skills add https://github.com/Vibecoder79/jarvis --skill implement-vibecoder79

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI-assisted coding often jumps straight from a ticket to code, skipping architecture review, dependency checks, governance validation, and acceptance criteria verification. This Skill enforces a non-skippable 8-step protocol that turns a Linear issue into shipped, validated code with full documentation and audit trail. ## Core Features & Use Cases - 8-Step Gated Workflow: Issue identification, dependency check, context building, governance validation, spec-file hard gate, plan approval, implementation, and post-implementation validation — no step can be skipped. - Machine-Enforced Spec Gate: Every code change requires a spec file at specs/ISSUE-XX.md before planning begins, enforced by git hooks (spec-gate.sh, doc-version-sync.sh, integration-test-gate.sh). - Post-Implementation Validation: ESLint quality gate, acceptance criteria verification with Linear comments, architecture quick-check, smoke test, and security findings documentation. - Use Case: A developer says "los" or runs /implement; the Skill picks up the "In Progress" Linear issue, validates dependencies and governance artifacts, creates or verifies the spec file, implements the change, runs all validation gates, updates docs and changelog, and closes the issue with a result table. ## Quick Start Say "implement the story" or run /implement to start the 8-step protocol on the current Linear issue marked In Progress.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I implement a Linear issue with a governed workflow?▼

Run /implement or say "los" with an issue marked In Progress in Linear. The Skill walks through 8 gated steps: identify the issue, check dependencies, build context, validate governance artifacts, pass the spec-file gate, get plan approval, implement, and run post-implementation validation before closing.

What is the spec-file gate and can it be skipped?▼

The spec-file gate requires a specs/ISSUE-XX.md file to exist before the planning step begins. It cannot be skipped for code changes — the git hook spec-gate.sh blocks any commit referencing an issue without its spec file. Only pure documentation commits are exempt.

Can this workflow run without human approval?▼

Yes, the protocol supports auto-execute mode under the Linear Automation Daemon, which skips the human-in-the-loop plan approval step when triggered by a webhook. All other gates, including the spec gate and validation steps, still apply.

What validation happens after implementation before closing an issue?▼

Post-implementation validation runs an ESLint quality gate (0 errors, 0 warnings), verifies every acceptance criterion with evidence in a Linear comment, performs an architecture quick-check, runs a real smoke test, and documents security findings. Only a PASS result moves the issue to Done.

What happens if a Linear issue is missing governance sections?▼

The Skill warns the operator about missing sections such as the 8-dimension table, security checklist, or acceptance criteria, and offers to add them retroactively. It never proceeds silently past governance gaps — they must be made visible first.