{"slug": "fluencyloop-a-lighter-developer-centric-speckit-alternative", "title": "FluencyLoop – A lighter, developer-centric SpecKit alternative", "summary": "FluencyLoop launches as a developer-centric alternative to SpecKit, offering a lightweight tool that documents AI-generated code by capturing design decisions, rationale, and reviewer-ready summaries within feature branches. The tool integrates with Claude Code and Codex, maintaining a private knowledge base to calibrate explanations based on developer familiarity, and stores documentation alongside code under docs/fluencyloop/. It aims to keep developers fluent in the code their AI agents write by producing documentation during delivery rather than after context is lost.", "body_md": "**Stay fluent in the code your AI agent writes.** FluencyLoop turns each feature into a documented\ndesign, teaches the decisions at your level, tracks the rationale, and produces a reviewer-ready\nsummary. A private knowledge base keeps that teaching calibrated across features.\n\nThe code and your fluency in it are produced together, or not at all.\n\nInitialize the project once, then run one feature loop per branch. Use **plan** only when the work\nis too large for a single feature.\n\n| Step | Claude Code | Codex | What it does |\n|---|---|---|---|\n1. Initialize |\n`fluencyloop init` |\n`fluencyloop init` |\nCreates the project state and an empty constitution. Plan and feature also do this automatically if needed. |\n2. Plan (optional) |\n`/fluencyloop:plan <initiative description>` |\n`$fluencyloop:plan <initiative description>` |\nDesigns the architecture and breaks a large initiative into feature-sized tasks. |\n3. Build + learn |\n`/fluencyloop:feature <feature description>` |\n`$fluencyloop:feature <feature description>` |\nCreates a feature branch and design, builds in slices, teaches each real decision, and journals it. |\n4. Review |\n`/fluencyloop:review` |\n`$fluencyloop:review` |\nAssembles the branch's sessions and decisions into a reviewer-facing PR view. |\n\nFor normal-sized work, the practical path is **init → feature → review**. For a large initiative,\nrun **plan** first, then repeat **feature → review** for each task in its roadmap.\n\nIf work was merged without the loop, use `/fluencyloop:backfill`\n\nin Claude Code or\n`$fluencyloop:backfill`\n\nin Codex to reconstruct and verify its design and decisions.\n\nThe constitution is a short set of checkable engineering principles for the project. It starts from the first real plan or feature and grows when a decision reveals a repeatable stance. Every later design and review is checked against it, but it never blocks a conventional merge.\n\nFluencyLoop teaches at the moment a meaningful decision is made. It explains the mechanism, the reason for the chosen path, and the rejected alternative, then checks that the explanation landed before continuing when the topic is unfamiliar.\n\nIt maintains a private, per-developer knowledge base of domain familiarity and demonstrated engagement. That profile carries across projects and features, keeping explanations concise on familiar ground and deeper where knowledge is still forming. It is never committed to a project; only person-neutral knowledge-transfer notes about the software enter the documentation.\n\nPlans, Mermaid design diagrams, feature sessions, and review summaries live beside the code under\n`docs/fluencyloop/`\n\n. They are created from the actual branch and its changes, so documentation is\nproduced during delivery rather than reconstructed after context has been lost.\n\nEach real fork records what was chosen, where it applies, why it was chosen, which alternative was rejected, how it relates to the constitution and design, and whether the rationale was verified. Reviewers get the decisions that shaped the feature instead of only a list of changed files.\n\n```\ndocs/fluencyloop/\n├── constitution.md\n├── plans/<initiative>/plan.md\n└── features/<feature>/\n    ├── design.md\n    └── sessions/*.md\n```\n\n`.fluencyloop/`\n\ncontains project workflow state. The per-developer calibration profile lives in\n`~/.fluencyloop/`\n\n; it controls teaching depth and is never committed. Session documents describe\nthe work, never the person.\n\n```\n/plugin marketplace add baokhang83/fluencyloop\n/plugin install fluencyloop@fluencyloop\n```\n\nUse the namespaced slash commands shown above. The plugin bundles its deterministic CLI, so there is no separate system-wide FluencyLoop installation.\n\n## Claude Code updates and Windows approvals\n\nFluencyLoop's startup hook checks its own marketplace on each new session and, when an update is\navailable, installs it for the next session without changing the active one. Run\n`/reload-plugins`\n\nto activate it in the current session instead. The check runs at startup only;\nresuming, clearing, or compacting a session does not repeat it.\n\nTo update at any time by hand, run `/plugin marketplace update fluencyloop`\n\n, then\n`/plugin update fluencyloop@fluencyloop`\n\n, and finally `/reload-plugins`\n\n.\n\nThe startup check is best-effort and deliberately silent, because a session must never fail to\nstart over an update it could not fetch. If the `claude`\n\nCLI is absent from the `PATH`\n\n, or the\nnetwork or a policy blocks the marketplace, the session starts normally and reports nothing. Run\n`claude plugin list`\n\nto see the version you are actually running, and use the manual commands\nabove if it looks stale.\n\nClaude Code's own **Enable auto-update** toggle (`/plugin`\n\n→ **Marketplaces** → **fluencyloop**)\nis a separate control that stays off by default. FluencyLoop refreshes only its own package and\ndoes not read or change that setting.\n\nOn native Windows, use the project-scoped setup in\n[Claude Code approvals](/baokhang83/fluencyloop/blob/main/docs/claude-code-permissions.md) to reduce routine FluencyLoop, editing,\nand read-only Git prompts without granting broad Git or Bash access.\n\n```\ncodex plugin marketplace add baokhang83/fluencyloop\ncodex plugin add fluencyloop@fluencyloop\n```\n\nUse the `$fluencyloop:<stage>`\n\nskills shown above. The plugin maintains its own `fluencyloop`\n\ncommand shim on macOS, Linux, Git Bash, and WSL; no separate runtime installation is required.\n\n## Codex updates\n\nCodex asks you to review FluencyLoop's startup hook once. Approve it from `/hooks`\n\nto enable\nautomatic updates. Each new session checks only FluencyLoop's marketplace and, when an update is\navailable, installs it for the next session without changing the active one.\n\nLike the Claude Code check, this one is best-effort and silent: an unapproved hook, a missing\n`codex`\n\nCLI, or a blocked marketplace leaves the session running its current version without\nreporting anything. Run `fluencyloop version`\n\nto see the version the Codex install is actually\nrunning. To update by hand, run `codex plugin marketplace upgrade fluencyloop`\n\n, then\n`codex plugin add fluencyloop@fluencyloop`\n\n; the next session picks it up.\n\nFluencyLoop requires [Claude Code](https://claude.com/claude-code) or\n[Codex](https://developers.openai.com/codex/), `git`\n\n, and either Bash on macOS/Linux/Git Bash/WSL\nor PowerShell (`pwsh`\n\n) on native Windows.\n\nRead [MANIFESTO.md](/baokhang83/fluencyloop/blob/main/MANIFESTO.md) for the product principles, calibration and privacy model, and\nthe boundary between deterministic tooling and agent reasoning. See [CONTRIBUTING.md](/baokhang83/fluencyloop/blob/main/CONTRIBUTING.md)\nfor the repository layout, test commands, and distribution notes.", "url": "https://wpnews.pro/news/fluencyloop-a-lighter-developer-centric-speckit-alternative", "canonical_source": "https://github.com/baokhang83/fluencyloop", "published_at": "2026-07-18 05:44:19+00:00", "updated_at": "2026-07-18 06:21:26.971009+00:00", "lang": "en", "topics": ["developer-tools", "ai-agents", "ai-tools"], "entities": ["FluencyLoop", "SpecKit", "Claude Code", "Codex"], "alternates": {"html": "https://wpnews.pro/news/fluencyloop-a-lighter-developer-centric-speckit-alternative", "markdown": "https://wpnews.pro/news/fluencyloop-a-lighter-developer-centric-speckit-alternative.md", "text": "https://wpnews.pro/news/fluencyloop-a-lighter-developer-centric-speckit-alternative.txt", "jsonld": "https://wpnews.pro/news/fluencyloop-a-lighter-developer-centric-speckit-alternative.jsonld"}}