skills.rest
dmae97
dmae97COMMUNITY
Explore all skills by this author →
GitHub

omk-flow-feature-dev

Implement new features end-to-end with quality checks and a final report.

130|14|Updated Apr 30, 2026
Search Tags:#planning#testing#code review#feature development#implementation#quality gates
One-click install
npx skills add https://github.com/dmae97/oh-my-kimi --skill omk-flow-feature-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omk-flow-feature-dev
Source: https://github.com/dmae97/oh-my-kimi/tree/main/templates/skills/kimi/omk-flow-feature-dev
Command: npx skills add https://github.com/dmae97/oh-my-kimi --skill omk-flow-feature-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you implement a new feature reliably by turning vague requests into a validated, test-backed change with a clear final report.

Core Features & Use Cases

  • Goal clarification and acceptance criteria: Locks down what “done” means before any coding starts.
  • Repository exploration and architecture summarization: Identifies the relevant files and how the system is structured to avoid random edits.
  • Implementation with quality gates and review: Executes the smallest complete change, runs lint/typecheck/tests/build when available, and loops until quality checks pass.
  • Use Case: You’re asked to add a new user-facing capability; the Skill guides you through planning affected areas, implementing the minimal correct change, fixing failures, and documenting what you shipped.

Quick Start

Use the omk-flow-feature-dev skill to build a small, testable implementation for a new feature you want to add, then produce a final report of the changes and commands run.

Frequently Asked Questions about omk-flow-feature-dev

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

FAQPage Schema
What is the best way to plan and implement a new feature end-to-end?▼

Feature development requires a structured approach that clarifies requirements, explores the repository, implements the smallest complete change, and validates it through iterative quality gates before final review.

How do I implement a new feature while ensuring my code passes quality checks?▼

You implement the change, then run lint, typecheck, tests, and build commands iteratively, looping to fix failures until all quality gates pass and the minimal correct change is complete.

How does feature development work when starting from vague requirements?▼

Feature development works by first locking down goal clarification and acceptance criteria, summarizing the architecture, and identifying affected files to prevent random edits during implementation.

Can I use this workflow for adding a small user-facing capability to an existing codebase?▼

Yes, you can use it to build a small, testable implementation for a new feature, guiding you through planning affected areas, fixing quality gate failures, and documenting the shipped changes.

Why do I need to run iterative quality gates during implementation?▼

Iterative quality gates are needed to resolve lint, typecheck, test, and build failures immediately, ensuring the implemented code meets validation standards before the final diff review and reporting.

Related Skills

Explore More Software Engineering Skills→
VYRE-StudiosVYRE-Studios

plan

Explore a codebase and produce ordered, testable implementation plans.

Official
Advanced
dmae97dmae97
130

omk-quality-gate

Execute or document quality-gate commands for linting, type checking, testing, and building.

Community
Intermediate
pantheon-orgpantheon-org
1

pr-iteration

Iteratively fix lint, typecheck, test, and build failures until CI passes.

Official
Intermediate
lix965996-artlix965996-art

paper-compile-zh

Compile Chinese LaTeX papers into validated PDFs using XeLaTeX and BibTeX.

Community
Advanced