jikime-workflow-spec

Orchestrate the SPEC workflow with EARS format and Plan-Run-Sync cycle.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a robust framework for managing software specifications using the EARS format, ensuring clear requirements, systematic planning, and seamless integration into the Plan-Run-Sync development lifecycle.

Core Features & Use Cases

  • EARS Format: Define requirements using Ubiquitous, Event-Driven, State-Driven, Unwanted, and Optional patterns for clarity.
  • Requirement Clarification: A systematic four-step process to refine and validate requirements.
  • Plan-Run-Sync Integration: Orchestrates the entire development workflow from planning to synchronization.
  • Parallel Development: Leverages Git Worktrees for isolated, parallel feature development.
  • Use Case: When planning a new feature, use this Skill to generate a detailed SPEC document that guides development, ensures all requirements are met, and facilitates collaboration among team members.

Quick Start

Use the jikime-workflow-spec skill to create a new SPEC for a user authentication system.

Frequently Asked Questions about jikime-workflow-spec

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

FAQPage Schema
What is the EARS format for requirement specification?

The EARS format structures requirement specification into Ubiquitous, Event-Driven, State-Driven, Unwanted, and Optional patterns to ensure clear, systematic requirements for software development workflows.

How do I create a SPEC document using a Plan-Run-Sync cycle?

You create a SPEC document by generating a 3-file structure containing spec.md, plan.md, and acceptance.md, which orchestrates the entire development workflow from planning to synchronization.

How does domain-driven design integrate with requirement clarification workflows?

Domain-driven design integrates with requirement clarification through a systematic four-step process that refines and validates requirements before generating detailed SPEC documents for development.

Can I use Git Worktrees for parallel feature development in a SPEC workflow?

Yes, the SPEC workflow leverages Git Worktrees to enable isolated, parallel feature development while maintaining adherence to the project constitution and metadata schema.

What is the TRUST 5 framework for quality validation in software planning?

The TRUST 5 framework provides quality validation during software planning, enforcing adherence to the project constitution and metadata schema throughout the SPEC workflow lifecycle.

Do I need a specific development methodology to use EARS requirement patterns?

EARS requirement patterns are designed for the JikiME-ADK development methodology, integrating EARS format with systematic clarification and the Plan-Run-Sync cycle for robust specification management.