popup-studio-ai/control
skills/control/SKILL.md
Control bkit automation level (L0-L4), view trust score, and manage guardrails. Trust level directly drives SPRINT_AUTORUN_SCOPE (v2.1.13): L0 manual+stopAfter=prd, L4 full-auto+stopAfter=archived. Also gates PDCA phase transitions and destructive operations. Triggers: control, automation level, trust score, guardrail, 자동화 레벨, 제어.
$ install --global
skillsauthnpx skillsauth add popup-studio-ai/bkit-claude-code controlInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 13, 2026, 6:27 AM139.9s1 file scanned
SKILL.md
- name:
- control
- classification:
- workflow
- classification-reason:
- Automation control persists regardless of model advancement
- deprecation-risk:
- none
- effort:
- medium
- description:
- |
- Control bkit automation level (L0-L4), view trust score, and manage guardrails. Trust level directly drives SPRINT_AUTORUN_SCOPE (v2.1.13):
- L0 manual+stopAfter=prd, L4 full-auto+stopAfter=archived. Also gates PDCA phase transitions and destructive operations.
- Triggers:
- control, automation level, trust score, guardrail, 자동화 레벨, 제어.
- argument-hint:
- [status|level|pause|resume|trust]
- user-invocable:
- true
- imports:
- []
- next-skill:
- null
- pdca-phase:
- null
- task-template:
- [Control] {action}
Control Skill
User-invocable skill for managing bkit automation level and system status.
Arguments
| Argument | Description | Example |
|----------|-------------|---------|
| (none) | Show current status (same as status) | /control |
| status | Show automation level, trust score, guardrails | /control status |
| level <0-4> | Set automation level manually | /control level 2 |
| pause | Pause all automation (equivalent to L0) | /control pause |
| resume | Resume to previous automation level | /control resume |
| trust | Show trust score details and history | /control trust |
Automation Levels
| Level | Name | Description | Approval Gates | |:-----:|------|-------------|----------------| | L0 | Manual | All actions require explicit user approval | Every phase transition | | L1 | Guided | Suggestions provided, user confirms each step | Every phase transition | | L2 | Semi-Auto | Routine transitions auto, key decisions gated | do->check, check->report, report->archive | | L3 | Auto | Most transitions auto, only destructive ops gated | report->archive | | L4 | Full-Auto | Fully automated PDCA cycle, minimal intervention | Initial feature approval only |
Action Details
status (Default)
Display the current automation control state.
- Read runtime control state from
.bkit/runtime/control-state.json - Read trust score from
.bkit/state/trust-score.json - Read active guardrails from
lib/control/configuration - Display formatted status panel
Output Format:
--- bkit Control Panel ----------------------------
Automation Level : L2 (Semi-Auto)
Trust Score : 72/100
Active Guardrails: 8/8
Paused : No
Features Active : 2/3
---------------------------------------------------
Guardrails:
[ON] Destructive operation detection
[ON] Blast radius limiter (max 10 files)
[ON] Loop breaker (max 5 iterations)
[ON] Checkpoint auto-creation
[ON] Permission escalation gate
[ON] Stale feature timeout (7d)
[ON] Context overflow protection
[ON] Concurrent write lock
---------------------------------------------------
level <0-4>
Set the automation level manually.
- Validate input is a number 0-4
- Read current level from
.bkit/runtime/control-state.json - If escalating (going higher), warn user about reduced oversight
- If de-escalating, apply immediately without confirmation
- Update
.bkit/runtime/control-state.jsonwith new level - Write audit log entry via
lib/audit/audit-logger.js - Display confirmation with new level details
Escalation Rule: Level increases require explicit confirmation via AskUserQuestion. Level decreases are immediate (safe direction).
Level Mapping to Automation: | Level | automationLevel | Description | |:-----:|:---------------:|-------------| | L0 | manual | All manual | | L1 | guide | Guided suggestions | | L2 | semi-auto | Semi-automatic (default) | | L3 | auto | Mostly automatic | | L4 | full-auto | Fully automatic |
pause
Pause all automation immediately.
- Save current level to
.bkit/runtime/control-state.jsonaspreviousLevel - Set level to L0 (Manual)
- Set
paused: trueflag - Write audit log:
automation_paused - Display confirmation: "Automation paused. All operations require manual approval."
resume
Resume automation to the previous level before pause.
- Read
previousLevelfrom.bkit/runtime/control-state.json - If not paused, display: "Automation is not paused."
- Restore level to
previousLevel - Clear
pausedflag - Write audit log:
automation_resumed - Display confirmation with restored level
trust
Show trust score details and contributing factors.
- Read trust score from
.bkit/state/trust-score.json - Calculate score breakdown:
- PDCA completion rate (0-25 points)
- Match rate average (0-25 points)
- Error recovery rate (0-20 points)
- Session stability (0-15 points)
- User override frequency (0-15 points, inverse)
- Display detailed breakdown
Output Format:
--- Trust Score Details ---------------------------
Overall Score: 72/100
Breakdown:
PDCA Completion Rate : 18/25 (72% cycles completed)
Match Rate Average : 22/25 (88% average)
Error Recovery Rate : 14/20 (70% recovered)
Session Stability : 12/15 (80% stable)
User Override Freq : 6/15 (40% override rate)
---------------------------------------------------
Level Recommendation: L2 (Semi-Auto)
Score 0-30 -> L0 (Manual)
Score 31-50 -> L1 (Guided)
Score 51-70 -> L2 (Semi-Auto)
Score 71-85 -> L3 (Auto)
Score 86+ -> L4 (Full-Auto)
---------------------------------------------------
State Files
| File | Purpose |
|------|---------|
| .bkit/runtime/control-state.json | Runtime control state (level, paused, previousLevel) |
| .bkit/state/trust-score.json | Trust score and contributing metrics |
Module Dependencies
| Module | Function | Usage |
|--------|----------|-------|
| lib/control/automation-controller.js | getLevel(), setLevel() | Read/write automation level |
| lib/control/automation-controller.js | pause(), resume() | Pause/resume automation |
| lib/audit/audit-logger.js | writeAuditLog() | Record control changes |
Usage Examples
# Check current status
/control
# Set to Semi-Auto
/control level 2
# Pause all automation
/control pause
# Resume previous level
/control resume
# View trust score
/control trust
Related Skills
popup-studio-ai/sprint
testing
VerifiedTrustedCommunity
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.
548SKILL.mdUpdated May 13, 2026
popup-studio-ai/cc-version-analysis
tools
VerifiedTrustedCommunity
CC CLI version upgrade impact analysis — research changes, analyze bkit impact, generate report. Triggers: cc-version-analysis, CC upgrade, version analysis, CC 버전 분석, 버전 영향.
545SKILL.mdUpdated Apr 18, 2026
popup-studio-ai/rollback
testing
VerifiedTrustedCommunity
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, 롤백, 체크포인트, 복원.
539SKILL.mdUpdated Apr 18, 2026
popup-studio-ai/qa-phase
testing
VerifiedTrustedCommunity
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.
539SKILL.mdUpdated Apr 18, 2026