Omkar Ambalal Kodmur

You can create feature specifications from natural language, clarify ambiguous requirements, generate implementation plans and design artifacts, produce dependency-ordered tasks.md files, execute all tasks, analyze cross-artifact consistency, converge codebases against specs, and convert tasks into GitHub issues.

Software engineers and technical leads practicing specification-driven development benefit most. They suit developers who want structured feature lifecycles—spec, plan, tasks, implementation, and consistency analysis—managed through markdown artifacts inside a standardized project structure.

Every skill requires an existing spec-kit project structure containing a .specify/ directory. The skills operate on markdown artifacts such as spec.md, plan.md, and tasks.md, so those templates and files must exist or be generated by earlier commands in the sequence.

Start with constitution and specify, then clarify to resolve ambiguities. Next run plan and tasks to produce design artifacts, optionally validate with checklist and analyze, then implement to execute tasks. Use converge to catch remaining work and taskstoissues to publish GitHub issues.

The skills are published publicly in Omkar-code-mur's GitHub repository and originate from github-spec-kit templates. No licensing fee or paid tier is indicated in the manifest; they are template-based markdown commands usable within any compatible spec-kit project.