agentleFS
ww-w-aiww-w-ai/bkit-claude-code/AGENTS.md

bkit-claude-code

AGENTS.md605 starsChanged 3 months agoApache-2.0View on GitHub

Sprint Management is a meta-container that groups one or more features under a shared scope, budget, and timeline. Each sprint runs its own 8-phase lifecycle: prd → plan → design → do → iterate → qa → report → archived. When the user mentions "sprint", invoke bkit:sprint skill (/sprint <action>). Sprint phases coexist with PDCA's 9-phase enum — both may track concurrently (see docs/06-guide/sprint-migration.guide.md). Trust Level scope (SPRINT_AUTORUN_SCOPE, L0–L4) controls auto-run boundaries. At L4 Full-Auto, the orchestrator advances phases until…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this AGENTS.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always respond in Korean (한국어) when communicating with the user.

    line 6
  2. Distinctive:

    Do NOT translate existing English files to Korean (waste of tokens)

    line 25
  3. Distinctive:

    Do NOT write docs/ files in English unless explicitly requested

    line 26
  4. Distinctive:

    Do NOT mix languages within a single file (except trigger keyword lists)

    line 27
  5. Very specific:

    When the user mentions "sprint", invoke bkit:sprint skill (/sprint <action>).

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md

bkit Project Rules

Language Rules

Conversation

  • Always respond in Korean (한국어) when communicating with the user.

Code & Documentation Language

  • English by default for ALL generated content:
    • Code, comments, commit messages, PR descriptions
    • README.md, CHANGELOG.md, and all non-docs/ markdown files
    • Agent definitions (agents/*.md), skill definitions (skills/*/SKILL.md)
    • Templates (templates/*.md)
    • Config files, error messages, log messages
  • Korean exceptions (한국어 작성):
    • docs/ directory and all subdirectories (docs/01-plan/, docs/02-design/, docs/03-analysis/, docs/04-report/)
    • 8-language auto-trigger keywords (EN, KO, JA, ZH, ES, FR, DE, IT) in agent/skill trigger lists
    • bkit memory state descriptions in .bkit/state/memory.json

Key Principle

bkit is a global service. Keep all public-facing and code-level content in English. Korean is only for internal planning docs (docs/) and developer communication.

Do NOT

  • Do NOT translate existing English files to Korean (waste of tokens)
  • Do NOT write docs/ files in English unless explicitly requested
  • Do NOT mix languages within a single file (except trigger keyword lists)

Sprint Management (v2.1.13)

Sprint Management is a meta-container that groups one or more features under a shared scope, budget, and timeline. Each sprint runs its own 8-phase lifecycle: prd → plan → design → do → iterate → qa → report → archived.

When the user mentions "sprint", invoke bkit:sprint skill (/sprint <action>). Sprint phases coexist with PDCA's 9-phase enum — both may track concurrently (see docs/06-guide/sprint-migration.guide.md).

Trust Level scope (SPRINT_AUTORUN_SCOPE, L0–L4) controls auto-run boundaries. At L4 Full-Auto, the orchestrator advances phases until any of 4 auto-pause triggers fires (quality gate fail / iteration exhausted / budget exceeded / phase timeout).

For deep-dive Korean guidance, see docs/06-guide/sprint-management.guide.md.

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.

Reviews can't be read right now.

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.