--- title: "nobrainer-tech-flow" description: "nobrainer-tech-flow: portable agentic workflows from task to checked result." canonical: https://agentpluginsdirectory.com/plugins/nobrainer-tech-flow last-updated: 2026-09-27 --- # nobrainer-tech-flow nobrainer-tech-flow: portable agentic workflows from task to checked result. - Slug: nobrainer-tech-flow - Publisher: NoBrainer Tech - Repository: https://github.com/nobrainer-tech/nobrainer-tech-flow - Manifest: plugin.json - Version: 2.0.0 - Category (editorial): other - Skills: 18 (nobrainer-auto-fine-tune, nobrainer-autoimprove, nobrainer-browser, nobrainer-build, nobrainer-codex-context, nobrainer-decide, nobrainer-dispatcher, nobrainer-rca, nobrainer-research, nobrainer-review, nobrainer-security, nobrainer-sessions, nobrainer-skill-doctor, nobrainer-spec-driven-development, nobrainer-team, nobrainer-tech-flow, nobrainer-wiki, nobrainer-writing) - MCP servers: 0 - Stars: 5 - Repository created: 2026-02-06 - Repository last pushed: 2026-09-26 - Publisher type: User - Listing: https://agentpluginsdirectory.com/plugins/nobrainer-tech-flow - Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json ## What nobrainer-tech-flow does, in the publisher's words nobrainer-tech-flow From task to done. Tell nobrainer-tech-flow what you need. It clarifies the goal, does the work, and checks the result. - BUDDY is the first and only ordinary clarification stage. - SCOPE freezes outcome, non-goals, expected files, proof, untouched work, minimum solution, test decision and clean completion before a non-trivial write. - One canonical plan owns TODO state; the owner sees only a compact Progress checklist and one next action. - A durable ledger adds exact identity, dependencies, checkpoints, retries and rollback only for cross-session, dependency-rich or consequential work. - AUTOPILOT continues through routine approved work without repeated check-ins. - nobrainer-team selects the minimum useful capabilities; nobrainer-dispatcher schedules only approved ready work in bounded batches; nobrainer-sessions creates or reuses exact visible sessions only when parallelism, isolation, handoff or independent evidence earns the cost. From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/nobrainer-tech/nobrainer-tech-flow/HEAD/README.md ## Skills - nobrainer-auto-fine-tune: Use when setting up nobrainer-tech-flow for the first time, when the owner says nb-auto-fine-tune, or when client capabilities, model routing, context or useful parallelism need recalibration. - nobrainer-autoimprove: Use when the owner says nb-autoimprove, deep-autoresearch, code-autoresearch, nobrainer-capture-lesson, or nobrainer-continuous-improvement; asks to improve a skill or prompt; or wants a measurable bounded baseline-variant-evaluation loop instead of one subjective rewrite. - nobrainer-browser: Use when the owner says nb-browser or nobrainer-browser, asks to inspect or operate a rendered website, attach to an existing approved Chrome/Edge session, restart an approved non-default Chromium profile for loopback CDP, reproduce a browser flow, run Playwright tests, or record and analyze a Play… - nobrainer-build: Use when the owner says nb-build, engineering-standards, or nobrainer-simplifier, or asks to implement or simplify an approved bounded code, configuration, documentation, or test change after outcome and acceptance are clear; apply the smallest verified edit with calibrated KISS, DRY, SOLID, YAGNI… - nobrainer-codex-context: Use when setting up, auditing or repairing one project's Codex context; use nb-codex-context to inspect AGENTS files, configured fallbacks and byte limits, then make one evidence-backed project-local context change without changing global Codex configuration by default. - nobrainer-decide: Use when choosing between options: just decide for a quick choice, decide or nb-decide for standard analysis, deep decide or deep-decide for deep analysis. Evaluate feasibility, reliability, total cost, delivery time, scale and reversibility. - nobrainer-dispatcher: Use when the owner says nb-dispatcher or nobrainer-dispatcher, or when an approved plan has multiple queued work units that require ready-set selection, dependency-aware ordering, bounded parallel batches, retry scheduling, or routing audited results to the next queued unit; do not use for one cohe… - nobrainer-rca: Use when the owner says nb-rca or deep-rca, or requests an evidence-bound diagnosis of what caused a specific observed incident, regression, test failure, outage, wrong value, or unexpected system behavior before proposing a fix. - nobrainer-research: Use when the owner says nb-research, asks to research or verify external information, when a task depends on current, niche, uncertain, high-stakes, or source-attributed facts, or when solving a problem requires current external evidence rather than a stable local diagnostic. - nobrainer-review: Use when the owner says nb-review, deep-audit, deep-code-review, or deep-autoreview; explicitly requests an evidence-gated CLOSEOUT, adversarial BUG_HUNT or RELEASE_GATE; or needs final findings filtered to verified actionable defects. Use nobrainer-build for ordinary implementation and correction… - nobrainer-security: Use when the owner says nb-security or security-review, requests a threat model or security review, or when a change crosses authentication, authorization, secrets, untrusted input, sensitive data, dependency, installer, or production trust boundaries. - nobrainer-sessions: Use when the owner says nb-sessions, nb-multi, session-handoff, session-restart, or nb-session-restart, or asks for visible named reusable multi-session work with exact identity, isolated write scopes, audited handoffs, recovery, or controlled parallelism; do not use for a coherent one-session task. - nobrainer-skill-doctor - nobrainer-spec-driven-development - nobrainer-team - nobrainer-tech-flow - nobrainer-wiki - nobrainer-writing Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.