harness-generating

Generates Harness specification documents, AGENTS.md, standards, and dev maps for projects.

840|261|Updated Apr 18, 2019
One-click install
npx skills add https://github.com/TencentBlueKing/bk-bcs --skill harness-generating
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-generating
Source: https://github.com/TencentBlueKing/bk-bcs/tree/main/.agents/skills/harness-engineering/harness-generating
Command: npx skills add https://github.com/TencentBlueKing/bk-bcs --skill harness-generating

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Setting up consistent AI-agent governance documentation (AGENTS.md, harness specs, coding standards, dev maps) for a project is manual and error-prone; this Skill automates context-aware generation and correction of those documents.

Core Features & Use Cases

  • Project Context Sensing: Detects project type, tech stack, existing Harness components, and environment tool gaps before generating anything.
  • Spec Document Generation: Produces AGENTS.md, glossary, five harness component docs (context engineering, architectural constraints, entropy management, tooling, execution & verification), and stack-matched standards presets.
  • Dev Map & IDE Integration: Generates docs/dev-map via graphify, syncs standards rules to Cursor/CodeBuddy/Claude, and runs harness-verify as a delivery gate.
  • Use Case: Point it at a monorepo with a Vue3 frontend and Gin backend; it detects both stacks, deploys frontend-vue3 and backend-gin standards, writes AGENTS.md with work-unit indexes, and outputs a summary report listing environment tool gaps.

Quick Start

Ask the agent to generate the Harness specification documents and standards for this repository.

Frequently Asked Questions about harness-generating

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

FAQPage Schema
How do I generate AGENTS.md and harness spec docs for my project?

Invoke the harness-generating flow through the parent harness-engineering skill. It senses project context, collects missing information, then generates AGENTS.md, docs/glossary.md, five harness component docs, and stack-matched standards under docs/standards/.

How does the skill detect which technology standards to deploy?

It runs detect-standards.sh against the workspace, which reads assets/standards/index.yaml and matches package.json or go.mod subproject roots against detect rules. Each category (frontend, api, backend) deploys its primary Level-1 preset; unmatched categories get no generic fallback.

Does it overwrite my existing AGENTS.md or business standards?

Existing root AGENTS.md is first understood per the agents-merge reference, then merged with RETAIN-ENTRY style decisions rather than blindly overwritten. The docs/business-standards/ directory is user-owned and never overwritten once it exists.

What happens if the graphify skill is not installed?

The dev-map generation step checks for skills/graphify/SKILL.md first. If missing, it skips knowledge graph generation, records the reason in the summary report, and continues with the remaining steps.

Why does harness-verify.sh fail before delivery?

harness-verify.sh is a hard gate that rejects false readiness claims in tooling.md, leftover workflow-agent sections, or TODO skeletons listed as selected standards. Fix the reported artifacts and rerun until it exits with code 0.