jikime-workflow-poc

Orchestrate phase-based development workflows for greenfield features using a POC-First methodology.

5|1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/jikime/jikime-adk --skill jikime-workflow-poc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jikime-workflow-poc
Source: https://github.com/jikime/jikime-adk/tree/main/templates/.claude/skills/jikime-workflow-poc
Command: npx skills add https://github.com/jikime/jikime-adk --skill jikime-workflow-poc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, phase-based workflow for developing new, greenfield features quickly and efficiently, prioritizing getting a working prototype first.

Core Features & Use Cases

  • POC-First Methodology: Focuses on "Make It Work" before refining.
  • Phase-Based Development: Guides through distinct stages: Make It Work, Refactor, Testing, Quality Gates, and PR Lifecycle.
  • Clear Transition Rules: Enforces strict phase progression and verification checkpoints.
  • Use Case: When starting a brand new feature, like a new user authentication module, this skill will guide the process from initial scaffolding to a merged pull request, ensuring a working, high-quality outcome.

Quick Start

Initiate the POC-First workflow for a new feature by running the jikime-workflow-poc skill.

Frequently Asked Questions about jikime-workflow-poc

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

FAQPage Schema
What is a phase-based development workflow for greenfield features?

A phase-based development workflow for greenfield features is a structured process that guides new code implementations through distinct stages, including Make It Work, Refactor, Testing, Quality Gates, and PR Lifecycle, ensuring rapid prototyping and structured quality improvement.

How does the POC-First methodology handle iterative development stages?

Phase-based development enforces strict transition rules and verification checkpoints between each iterative stage. This structured progression ensures developers cannot advance from Make It Work to Refactor, Testing, Quality Gates, or PR Lifecycle without passing required quality criteria.

How do I rapidly prototype a new feature from scaffolding to merged pull request?

To rapidly prototype a new feature, initiate the POC-First workflow to guide the process from initial scaffolding through iterative development stages. It manages the progression to a merged pull request, ensuring a working, high-quality outcome.

Can I use this workflow for adding new user authentication modules to an existing system?

Yes, you can use this workflow for adding new user authentication modules. It is designed specifically for developing new, greenfield features quickly and efficiently, guiding the entire process from initial scaffolding to a merged pull request.

When should I not use a POC-First approach for software engineering?

You should not use a POC-First approach for modifying existing codebases or non-greenfield development. This workflow is specifically designed to orchestrate phase-based development for brand new features rather than updating or refactoring legacy systems.