mk.workflow

Automate specification, planning, and task generation workflows in Claude Code.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mayknxyz/my-kit --skill mk-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mk.workflow
Source: https://github.com/mayknxyz/my-kit/tree/main/kit/.claude/skills/mk.workflow
Command: npx skills add https://github.com/mayknxyz/my-kit --skill mk-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Automates the end-to-end development workflow inside Claude Code, guiding users from issue intake to plan, tasks, and implementation while enforcing project conventions.

Core Features & Use Cases

  • Auto-trigger mapping to 7 steps for specification, planning, tasks, and implementation
  • Load and manage branch context and references (fetch-branch-info, spec.md, plan.md, tasks.md)
  • Interactive ambiguity reduction and alignment with CLAUDE.md patterns
  • Optional artifacts support: clarify, checklist, and analyze for quality and governance
  • Guidance for artifact generation and discovery across the full lifecycle
  • Read-only analysis and governance checks to maintain consistency

Quick Start

Start with /mk.specify <issue-number> to create a spec, then use /mk.plan and /mk.tasks to generate the plan and tasks.

Frequently Asked Questions about mk.workflow

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

FAQPage Schema
How do I automate the development workflow from issue intake to implementation in Claude Code?

To automate the development workflow, use commands like /mk.specify with an issue number to generate specifications, then proceed to generate plans and tasks for implementation while enforcing project conventions.

What is the best way to align generated plans and tasks with existing CLAUDE.md conventions?

Aligning plans with CLAUDE.md conventions involves loading branch context and resolving issues to ensure generated artifacts like spec.md and plan.md maintain consistent discovery and activation patterns across the project.

Does this workflow automation support optional artifacts like checklists and analyses for governance?

Yes, optional artifacts including clarify, checklist, and analyze are supported to provide governance checks and maintain quality throughout the specification, planning, and implementation phases.

Can I manage branch context and references like spec.md and tasks.md automatically?

You can automatically load and manage branch context and references by fetching branch info and generating specification, plan, and task documents to maintain a structured development workflow.

How do I start the 7-step development workflow using a single issue number?

Begin the 7-step workflow by executing the specify command with your issue number to create a spec, then sequentially use the plan and tasks commands to generate the required implementation artifacts.