agentleFS
Sign inStart free
alphazedealphazede/bearing-lite/skills/intake/SKILL.md

intake

Skill3 starsChanged 3 months agoApache-2.0View on GitHub

Verify and propose one target repository and plan directory when repository identity is absent or ambiguous. Use for Intake before Architectural Alignment. Do not use after owner-confirmed fit, for parent-wide exploration, planning decisions, product edits, role routing, or publication.

34 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use plan, triage and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 4 projects that use this

  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 4 projects that use this

  • AWSSkill

    retro

    Conduct a retrospective on a coding session.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    build

    Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.

    Also in 3 projects that use this

  • VercelSkill

    deploy

    Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".

    Also in 3 projects that use this

  • Microsoft AzureSkill

    verify

    End-to-end app testing pipeline for browser-based web apps on cloud browsers via Azure Playwright Workspaces: verify the live app, author tests for working flows, heal failing tests, then re-run with video and produce one consolidated report. Three phases (app verification, test authoring, test healing) plus a scoped final sanity run; each phase emits a sub-report. Use when asked to "verify my app", "make sure my app works and has good test coverage", "do a full QA pass", "add tests where I'm missing coverage", "fix failing tests and add new ones", "smoke test before deploy", "QA my deployment", or any combined verify-and-test ask. Requires Azure CLI (`az login`) and a Playwright Workspace resource ID — bootstraps configs on first invocation. Browser-based web apps with Playwright only — not for unit/API tests, native mobile/desktop, load/perf, or full accessibility audits.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 33 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never write files, walk unapproved parents, rank endless alternatives, or advance the Lifecycle itself.

    line 40

“Common” is measured: kept by at least 6 in 10 of the 33 edited versions of this file we could read. “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

Intake

The Orchestrator runs this in its controller session and records the decision. Intake handles input and repository selection.

Inputs and match

  • Inputs: Lifecycle goal, authorized candidate roots, visible prior decisions, repository rules, and discovery limits.
  • Match: target root, repository identity, or plan location is unresolved.
  • Non-match: the owner already named and confirmed the repository and plan.

Algorithm

  1. Inspect the selected root only. Open one additional root only when authorized.
  2. Cap discovery at depth 4 and 200 paths; prefer Git identity, manifests, top-level instructions, and current plan conventions.
  3. Reject nested-repository confusion, missing Git identity, or conflicting owner evidence with a typed finding.
  4. Propose exactly one repository and one plan-directory assumption with path evidence and a short reason.
  5. Return one owner confirmation question through the Orchestrator. A recommendation is not confirmation.

Return and recovery

Return FIT_PROPOSED, FIT_CONFIRMED, FIT_UNAVAILABLE, FIT_MALFORMED, or FIT_UNDECIDABLE with root, plan directory, evidence, blocker, and next action. Resume only from new evidence; never repeat confirmed input or add agent runs.

Never write files, walk unapproved parents, rank endless alternatives, or advance the Lifecycle itself.

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.

Check your setup, free