implement

Implements work items from specs or tickets using test-driven development.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/ZubairImtiaz3/Safar-E-Iman-Portal --skill implement-zubairimtiaz3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/ZubairImtiaz3/Safar-E-Iman-Portal/tree/main/.agents/skills/implement
Command: npx skills add https://github.com/ZubairImtiaz3/Safar-E-Iman-Portal --skill implement-zubairimtiaz3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or set of tickets into working, verified code requires discipline: writing tests first, running typechecks, and reviewing the result. This Skill guides the AI through that structured implementation workflow so nothing is skipped. ## Core Features & Use Cases - Spec-Driven Implementation: Builds the work described in a spec or ticket set, following test-driven development at pre-agreed seams. - Continuous Verification: Runs typechecking and individual test files regularly, then the full test suite once at the end. - Built-In Review and Commit: Finishes by invoking a code review pass and committing the work to the current branch. - Use Case: You have a ticket describing a new API endpoint. Invoke this Skill to implement it with TDD, verify types and tests, review the changes, and commit them to your branch. ## Quick Start Implement the work described in the current spec or tickets using test-driven development, then review and commit it.

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 from a spec using AI?

Provide the spec or tickets and invoke the implement Skill. It builds the work using test-driven development at pre-agreed seams, runs typechecking and tests along the way, then reviews and commits the result.

How does test-driven development fit into this workflow?

The Skill applies TDD at pre-agreed seams, meaning tests are written where the team has agreed test boundaries exist. It runs single test files regularly during development and the full test suite once at the end.

Does the implement Skill commit code automatically?

Yes, after implementation and code review are complete, the Skill commits the work to the current branch. It does not create new branches or push to remotes on its own.

When should I not use a spec-driven implementation workflow?

Avoid it for exploratory prototyping or spikes where requirements are unclear, since the workflow assumes a defined spec or tickets. It also expects an existing test setup to support the TDD steps.

Can the implement Skill be invoked automatically by the AI?

No, the Skill sets disable-model-invocation and disallows implicit invocation, so it only runs when the user explicitly calls it. This prevents unintended code changes and commits.