keqian-method

Guides AI-native product development using document-driven workflows, quality gates, and single-agent execution.

706|130|Updated Oct 31, 2025
One-click install
npx skills add https://github.com/staruhub/ClaudeSkills --skill keqian-method
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: keqian-method
Source: https://github.com/staruhub/ClaudeSkills/tree/main/skills/Geek-skills-keqian-method
Command: npx skills add https://github.com/staruhub/ClaudeSkills --skill keqian-method

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Building software with AI agents often fails because long task chains multiply small errors into broken results, token costs spiral, and agents resist or drift from requirements. This Skill provides a complete methodology for AI-native product development that keeps quality verifiable and costs under control.

Core Features & Use Cases

  • Document-Driven Development (SDD): Establishes a documentation hierarchy from PRD to technical specs before any code is written, with rules for keeping docs and code in sync.
  • Quality Gates and Eval Patterns: Defines action-eval pairs, phase gates, and acceptance thresholds so every agent output is verified, auto-repaired, or escalated to a human.
  • Single-Agent-First Execution: Provides decision rules for when to use one agent versus parallel subagents, plus strategies for context compaction and model selection.
  • Token Cost Optimization: Explains how strict quality gates raise cache hit rates, counterintuitively lowering total cost.
  • Use Case: You want to build a CRUD admin tool with Claude Code from requirements to passing tests. The Skill walks you through writing the PRD and architecture docs first, defining evals per task, then letting the agent execute sequentially through quality gates.

Quick Start

Use the keqian-method skill to design a document-driven development workflow with quality gates for my new AI-assisted project.

Frequently Asked Questions about keqian-method

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

FAQPage Schema
How do I set up document-driven development with AI coding agents?

Write the PRD and technical architecture documents before any code, then let the agent implement against them. Each feature needs multiple use cases in the spec, and documentation updates should be triggered automatically when code changes.

When should I use a single agent versus multiple parallel agents?

Default to a single agent for tasks with dependencies, long context chains, or high quality requirements. Use parallel subagents only when tasks are clearly independent and results merge cleanly, since context injection and result merging are common failure points.

How do quality gates reduce AI coding token costs?

Strict gates force repeated fixes on the same context, which raises cache hit rates dramatically. Cached tokens cost almost nothing, so burning more tokens on automated repair loops actually lowers total cost while improving quality.

What is an acceptable eval threshold for AI-generated code?

Thresholds depend on the scenario: around 95% for core business logic, 90% for documentation and tests, and 70% for exploratory tasks. Expect 3 to 5 iteration rounds rather than one-shot success, and define acceptable results within your budget and time constraints.

When should I not use this development methodology?

Skip it for single bug fixes or small changes that need no process overhead, and for PRD writing itself, which belongs to product management tooling. Open-ended AI-native products with unpredictable user behavior should use the xuefeng-method skill instead.