skills/pdca-fast-track/SKILL.md
Daniel-mode fast-track auto-approves Checkpoint 1-8 when Trust ≥ 80, fastTrack on, Design doc exists. Else L2 + manual gates. Triggers: pdca fast-track, skip checkpoints, auto approve, 패스트 트랙, ファストトラック, 快速通道, vía rápida.
npx skillsauth add popup-studio-ai/bkit-claude-code pdca-fast-trackInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
v2.1.11 Sprint β FR-β5. Wraps
lib/control/fast-track.js. Provides a single auto-escalation gate for users who have already earned Trust ≥ 80 and produced a Design doc — Checkpoints 1-8 default to Recommended without prompting. Falls back to L2 + manual review the moment any preconditions fails (E-β5-01 / E-β5-02).
| Argument | Description | Example |
|----------|-------------|---------|
| <feature> | Feature name to engage fast-track for | /pdca-fast-track bkit-v2111-integrated-enhancement |
bkit.config.json#control.fastTrack.enabled === true.bkit/state/trust-profile.json#trustScore
≥ fastTrack.minTrustScore (default 80)bkit.config.json#pdca.docPaths.design
templates against <feature>When any block, surface the reason with a remedy hint:
| Block | Remedy hint |
|-------|-------------|
| disabled_in_config | "Set control.fastTrack.enabled = true in bkit.config.json" |
| trust_score_too_low | "Run a few /pdca check cycles to raise trust" |
| design_doc_missing | "Run /pdca design <feature> first" |
fastTrack.autoLevel
(default L3)..bkit/runtime/fast-track-log.json:
{
"engaged": true,
"feature": "<feature>",
"engagedAt": "<ISO>",
"trustScore": 85,
"autoLevel": "L3",
"fallbackLevel": "L2",
"skipCheckpoints": [1,2,3,4,5,6,7,8],
"designPath": "docs/02-design/features/<feature>.design.md",
"decisions": []
}
fast-track.recordCheckpoint
to append a decision entry (audit trail).recordCheckpoint({ decision: 'fallback', reason: 'no_recommended' })
and pause to fallbackLevel.process.env.CLAUDE_PROJECT_DIR (or repo root).checkpoint (number), decision (enum), reason
(sanitized string).bkit.config.json — no traversal
via untrusted feature arg (pattern is {feature} placeholder only).| Module | Function | Usage |
|--------|----------|-------|
| lib/control/fast-track.js | evaluatePreconditions(feature) | Block list |
| lib/control/fast-track.js | engage(feature) | Audit + record |
| lib/control/fast-track.js | recordCheckpoint({...}) | Per-CP decision |
| lib/control/fast-track.js | isCheckpointSkipped(n) | Should we skip? |
# Engage on a Design-complete feature
/pdca-fast-track bkit-v2111-integrated-enhancement
# Result if Trust < 80
# Block: trust_score_too_low (current 68 < required 80)
# Result if Design missing
# Block: design_doc_missing → run /pdca design first
/control trust — current Trust Score breakdown/control level <0-4> — manual override/pdca-watch — observe progress while fast-tracking/pdca design <feature> — required prerequisiteARGUMENTS:
testing
Sprint Management — generic sprint capability for ANY bkit user. 16 sub-actions: init, start, status, watch, phase, iterate, qa, report, archive, list, feature, pause, resume, fork, help, master-plan. Triggers: sprint, sprint start, sprint init, sprint status, sprint list, 스프린트, 스프린트 시작, 스프린트 상태, スプリント, スプリント開始, スプリント状態, 冲刺, 冲刺开始, 冲刺状态, sprint, iniciar sprint, estado sprint, sprint, demarrer sprint, statut sprint, Sprint, Sprint starten, Sprint Status, sprint, avviare sprint, stato sprint, master plan, multi-sprint plan, sprint master plan, 마스터 플랜, 멀티 스프린트 계획, 스프린트 마스터 플랜, マスタープラン, マルチスプリント計画, スプリントマスタープラン, 主计划, 多冲刺计划, 冲刺主计划, plan maestro, plan multi-sprint, plan maestro sprint, plan maître, plan multi-sprint, plan maître sprint, Masterplan, Multi-Sprint-Plan, Sprint-Masterplan, piano principale, piano multi-sprint, piano principale sprint.
tools
CC CLI version upgrade impact analysis — research changes, analyze bkit impact, generate report. Triggers: cc-version-analysis, CC upgrade, version analysis, CC 버전 분석, 버전 영향.
testing
Manage PDCA checkpoints and rollback — create, list, restore for safe recovery. Rollback events are recorded via lib/audit/audit-logger ACTION_TYPES.rollback_executed. For sprint-level recovery, individual feature rollbacks may be triggered from within sprint phases (sprint itself is forward-only — terminal state is `archived`, not rolled back; v2.1.13). Triggers: rollback, checkpoint, restore, undo, 롤백, 체크포인트, 복원.
testing
QA Phase execution — L1-L5 test planning, generation, execution, and reporting for a single feature. For sprint-level QA (7-Layer dataFlowIntegrity / S1 gate across multiple features) use /sprint qa <sprintId> which delegates to sprint-qa-flow agent (v2.1.13). Triggers: qa phase, QA test, qa run, QA 실행, QAフェーズ, QA阶段, fase QA, phase QA, QA-Phase, fase QA.