agentleFS
popup-studio-aipopup-studio-ai/bkit-claude-code/skills/pdca-fast-track/SKILL.md

pdca-fast-track

Skill605 starsChanged 3 months agoApache-2.0View on GitHub

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

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When any block, surface the reason with a remedy hint:

    line 46
  2. Very specific:

    If a Checkpoint surfaces NO "Recommended" option, call recordCheckpoint({ decision: 'fallback', reason: 'no_recommended' }) and pause to …

    line 74
  3. Very specific:

    All file IO is rooted at process.env.CLAUDE_PROJECT_DIR (or repo root).

    line 80

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

PDCA Fast Track — Daniel's Track

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).

Arguments

ArgumentDescriptionExample
<feature>Feature name to engage fast-track for/pdca-fast-track bkit-v2111-integrated-enhancement

Behavior

Preconditions (all must pass; fail-open)

  1. Config enabled — bkit.config.json#control.fastTrack.enabled === true
  2. Trust Score ≥ 80 — .bkit/state/trust-profile.json#trustScore ≥ fastTrack.minTrustScore (default 80)
  3. Design doc exists — resolved via bkit.config.json#pdca.docPaths.design templates against <feature>

When any block, surface the reason with a remedy hint:

BlockRemedy 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"

On engage (all preconditions pass)

  1. Recommend Automation Level escalation L2 → fastTrack.autoLevel (default L3).
  2. Persist engagement record to .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": []
    }
  3. Each Checkpoint 1-8 invocation calls fast-track.recordCheckpoint to append a decision entry (audit trail).
  4. If a Checkpoint surfaces NO "Recommended" option, call recordCheckpoint({ decision: 'fallback', reason: 'no_recommended' }) and pause to fallbackLevel.

Security

  • All file IO is rooted at process.env.CLAUDE_PROJECT_DIR (or repo root).
  • Audit log JSON is OWASP A08-clean: no user-controlled keys; only whitelisted checkpoint (number), decision (enum), reason (sanitized string).
  • Design doc patterns are read from bkit.config.json — no traversal via untrusted feature arg (pattern is {feature} placeholder only).
  • Trust score read is fail-safe: missing file returns 0 (blocks engage).

Module Dependencies

ModuleFunctionUsage
lib/control/fast-track.jsevaluatePreconditions(feature)Block list
lib/control/fast-track.jsengage(feature)Audit + record
lib/control/fast-track.jsrecordCheckpoint({...})Per-CP decision
lib/control/fast-track.jsisCheckpointSkipped(n)Should we skip?

Examples

# 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

Related

  • /control trust — current Trust Score breakdown
  • /control level <0-4> — manual override
  • /pdca-watch — observe progress while fast-tracking
  • /pdca design <feature> — required prerequisite

ARGUMENTS:

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.