implement

Automate end-to-end feature implementation workflows from planning to testing.

17|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/alexiolan/craft-skills --skill implement-alexiolan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/alexiolan/craft-skills/tree/main/skills/implement
Command: npx skills add https://github.com/alexiolan/craft-skills --skill implement-alexiolan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly implement well-understood features by coordinating planning, parallel development, and testing, reducing cycle time.

Core Features & Use Cases

  • Quick architect-led planning to create a clear development plan.
  • Parallel development and browser testing to accelerate delivery.
  • Structured end-to-end workflow with a final report and iterative sign-off.

Quick Start

Describe your feature and let the implement skill coordinate planning, development, and testing.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I automate end-to-end feature implementation from planning to testing?

Automating end-to-end feature implementation requires a structured workflow that coordinates architect planning, parallel development, and browser-based testing to reduce cycle time. This skill manages the entire process from prompt-driven requirements to a final review report.

What is the best way to coordinate parallel development for well-understood software features?

Coordinating parallel development for well-understood features works best with an architect-led planning phase that creates a clear prompt-driven plan. This approach enables simultaneous development streams and browser testing, concluding with iterative sign-off and a structured final report.

Can I use prompt-driven planning for web and software feature development?

Yes, you can use prompt-driven planning for web and software feature development when requirements are clear and well-understood. The process applies an architect phase to guide requirements, followed by parallel development and browser-based testing.

How do I set up browser-based testing within an automated feature implementation workflow?

Setting up browser-based testing within an automated feature implementation workflow occurs after the architect planning and parallel development phases. It validates the developed features before moving to the final review and sign-off stage.

When should I avoid using an automated end-to-end implementation workflow?

You should avoid using an automated end-to-end implementation workflow when dealing with unclear or poorly understood requirements. This process specifically targets well-understood features across web and software projects to accelerate delivery.