agentleFS
Sign inStart free
mikhailkogan17mikhailkogan17/cycler/skills/workflow-intake/SKILL.md

workflow-intake

Skill0 starsChanged 17 days agoMITView on GitHub

OPTIONAL manual intake, run by hand rather than dispatched — write a task contract by hand, then pass contractPath to /workflow-feature. For full automation just use /workflow-feature directly.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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. Very specific:

    Use the tools available in your runtime.

    line 12
  2. Very specific:

    READ ${CLAUDE_PLUGIN_ROOT}/harness/HARNESS.md and ${CLAUDE_PLUGIN_ROOT}/harness/CONTRACT.md first.

    line 21
  3. Distinctive:

    Run git status --short. Do NOT touch existing uncommitted changes.

    line 25
  4. Distinctive:

    Do minimal READ-ONLY probing of the files the request names.

    line 26

≈ “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

Runtime compatibility (read first)

These instructions apply to Claude Code, Codex and DeepSeek Harness (dsh). Resolve CYCLER_ROOT from the environment, CLAUDE_PLUGIN_ROOT, or this skill's directory (../..). CLAUDE_PLUGIN_ROOT in the legacy instructions below is a compatibility alias for that root; CLAUDE_CODE_SESSION_ID may be replaced with CYCLER_SESSION_ID or the current runtime session ID. Use the tools available in your runtime; ToolSearch is not a prerequisite for research or Linear.

/workflow-intake — manual contract authoring (optional)

For full automation, just use /workflow-feature — it authors the contract itself. Use /workflow-intake when you want manual control of the contract before any code runs.

READ ${CLAUDE_PLUGIN_ROOT}/harness/HARNESS.md and ${CLAUDE_PLUGIN_ROOT}/harness/CONTRACT.md first.

Actions (in order)

  1. Run git status --short. Do NOT touch existing uncommitted changes.
  2. Do minimal READ-ONLY probing of the files the request names.
  3. Copy ${CLAUDE_PLUGIN_ROOT}/harness/CONTRACT.md to .claude/harness/contracts/<slug>.md.
  4. Fill every section from the user's words. If ambiguous, ASK (AskUserQuestion) — do not guess. Acceptance checks must be EXACT runnable commands.
  5. Show the user the contract + open questions/assumptions. Adjust until they confirm.

Output

  • .claude/harness/contracts/<slug>.md.

Stop condition

  • You MUST NOT edit code or run non-read-only commands.
  • Once confirmed, tell the user to run /workflow-feature with contractPath set to this contract.

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