skills.rest
TencentBlueKing
TencentBlueKingOFFICIAL
Explore all skills by this author →
WebsiteGitHub

lightweight-ai-workflow

Routes AI coding tasks into lightweight, OpenSpec, or multi-agent workflows with checklists.

2.5k|524|Updated May 29, 2019
Search Tags:#impact analysis#ai coding#openSpec#verification checklist#workflow triage#Multi-Agent#bk-ci
One-click install
npx skills add https://github.com/TencentBlueKing/bk-ci --skill lightweight-ai-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lightweight-ai-workflow
Source: https://github.com/TencentBlueKing/bk-ci/tree/main/ai/skills/lightweight-ai-workflow
Command: npx skills add https://github.com/TencentBlueKing/bk-ci --skill lightweight-ai-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When working on BK-CI with AI assistance, it is hard to decide how much process a task needs: a quick direct implementation, an impact analysis, an OpenSpec change document, or full multi-agent collaboration. This Skill provides a lightweight triage entry point that classifies each coding task and produces the right checklists, preventing both over-engineering small tasks and under-planning large ones.

Core Features & Use Cases

  • Task Triage: Classifies tasks into lightweight flow, impact-first analysis, OpenSpec, or multi-agent tracks based on module scope, risk, and contract changes.
  • Impact Checklist: Guides pre-implementation analysis of affected layers (Resource, Service, DAO, Model, config, frontend, Worker, Agent), APIs, data contracts, permissions, i18n, and rollback needs.
  • Verification Checklist: After implementation, records which requirements were covered, which builds/tests/lints ran, what was not verified, and remaining risks.
  • Use Case: Before modifying a BK-CI pipeline API, use this Skill to determine that the change touches a stable external contract, triggering the OpenSpec flow with documentation before any code changes.

Quick Start

Ask the AI to triage your BK-CI coding task and decide whether it needs a lightweight flow, an impact checklist, OpenSpec, or multi-agent collaboration.

Frequently Asked Questions about lightweight-ai-workflow

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

FAQPage Schema
How do I decide if a coding task needs OpenSpec documentation?▼

A task needs OpenSpec when it adds or modifies APIs, data structures, database scripts, or stable external contracts, spans more than two microservices or core modules, or involves permissions, compatibility, migration, rollout, or rollback. Unclear acceptance criteria also trigger OpenSpec.

When should I use a multi-agent workflow for coding tasks?▼

Use multi-agent collaboration when the requirement is large with unclear module ownership, when work must be handed off across requirement, design, implementation, and quality phases, when a single agent fails to converge after two rounds, or when the user explicitly requests it.

What is an impact checklist in AI-assisted development?▼

An impact checklist is a pre-implementation analysis listing affected layers such as Resource, Service, DAO, Model, configuration, frontend, Worker, and Agent, plus API, data contract, permission, i18n, event, cache, and scheduled task impacts. It is required for cross-module or unclear-call-chain tasks.

When should I not use this lightweight workflow skill?▼

Skip it when the task clearly belongs to a specific business module with its own skill, when an OpenSpec change directory already exists for the work, or when the question is purely conceptual and involves no delivery process.

What should a verification checklist include after implementation?▼

It should confirm each requirement is covered, record which builds, unit tests, lints, or key scripts ran, explain what was not verified and why, note any new warnings or failures, and list remaining risks or items needing manual confirmation.

Related Skills

Explore More Software Engineering Skills→
ishandutta2007ishandutta2007
13

Codebase Onboarding

Map unfamiliar codebases by identifying core modules, domain language, and architectural patterns.

Community
Intermediate
evandrodevbrevandrodevbr
1

openspec-apply-change

Implement OpenSpec change tasks by coordinating workflow selection and artifact review.

Community
Advanced
agent0aiagent0ai
1.4k

Documentation

Guide documentation reads and confirm AGENTS.md contracts before code edits.

Official
Basic
ngmthaqngmthaq

technical-leader-job-protocols

Coordinate technical leadership processes with Pre-Flight confirmation and stage-based planning.

Community
Advanced