agentleFS
jerssonjersson/jenie-ai-tools/skills/prepare-for-wishes/SKILL.md

prepare-for-wishes

Skill2 starsChanged 56 days agoMITView on GitHub

Entry point skill that loads all global guidelines, analyzes the project's technical context (if a repo exists), announces readiness, and asks what the developer wants to do — redirects to list-tasks, analyze-task, or implement-task as needed.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 4 are distinctive, and 7 are 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.

  • 7

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When this skill is loaded, you are the entry point.

    line 8
  2. Very specific:

    Read ../globals/INDEX.md and follow its instructions to load all globals.

    line 16
  3. Very specific:

    Check whether <project_root>/.git exists (use ls or test -d).

    line 20
  4. Very specific:

    Check whether <project_root>/.jenie/technical-context.md already exists (use ls or test -f).

    line 24
  5. Distinctive:

    If invoked explicitly (not as precondition): Always regenerate.

    line 26
  6. Very specific:

    If it exists and was generated less than 7 days ago: Read and cache. Skip re-analysis.

    line 28
  7. Distinctive:

    Otherwise: Run analysis to regenerate.

    line 29
  8. Very specific:

    Write the results to <project_root>/.jenie/technical-context.md.

    line 33
  9. Very specific:

    After writing, read the file back and cache its contents in context.

    line 35
  10. Distinctive:

    After outputting the warning, proceed to the Workflow section.

    line 41
  11. Very specific:

    When no specific intent is detected, greet the developer.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Prepare for Wishes Skill

When this skill is loaded, you are the entry point. Load the global configuration, analyze the project's technical landscape, then ask the developer what they need.

Command syntax: jenie commands are written here as /jenie <name>. In OpenCode use them as-is (e.g., /jenie list-tasks); in Claude Code they are namespaced with a colon (e.g., /jenie:list-tasks); in Copilot use the skill name directly (e.g., /list-tasks). Always show the developer the syntax that matches the current environment.

Pre-condition

1. Load Global Guidelines

Read ../globals/INDEX.md and follow its instructions to load all globals. Cache them for the session. This must complete before any workflow step.

2. Analyze source code repository

Check whether <project_root>/.git exists (use ls or test -d).

If .git exists (project has a source code repository)

Check whether <project_root>/.jenie/technical-context.md already exists (use ls or test -f).

  • If invoked explicitly (not as precondition): Always regenerate.
  • If invoked as precondition (from implement-task):

    • If it exists and was generated less than 7 days ago: Read and cache. Skip re-analysis. Check the Generated timestamp in the Cache section.
    • Otherwise: Run analysis to regenerate.

    When using MCP, include: Layers (internal/core/entry/leaf) and Boundaries (call flow between modules).

Write the results to <project_root>/.jenie/technical-context.md. Create the .jenie/ directory first if it does not exist. Use the template in ./guidelines/technical-context-template.md as the output format. Generate timestamps using the current UTC time (e.g., new Date().toISOString() in Node.js).

After writing, read the file back and cache its contents in context. The summary is available for the rest of the session — any downstream skill can reference .jenie/technical-context.md for project technical context.

If .git does not exist

⚠️ Warning: No source code repository detected at <project_root>. The prepare-for-wishes process will continue without technical understanding of the project. Some features (code cross-check, automated implementation) will be unavailable until a repository is initialized.

After outputting the warning, proceed to the Workflow section.

Workflow

1. Determine intent

If the developer asks to…Then…
list, browse, or show tasksRedirect to /jenie list-tasks and stop
validate, analyze, or review a taskRedirect to /jenie analyze-task and stop
implement or code a taskRedirect to /jenie implement-task and stop
prepare or nothing specific yetAnnounce readiness and present available commands

2. Announce readiness

When no specific intent is detected, greet the developer. Include the technical context in your announcement if a repo was analyzed (e.g., "Technical context loaded — <runtime> + <framework> project, <script_count> scripts available"):

Jenie is ready. What would you like to do?

  • /jenie list-tasks — Browse available tasks (user stories or bugs)
  • /jenie analyze-task — Validate consistency of a specific task with INVEST + 3C
  • /jenie implement-task — Implement a validated task end-to-end (branch, TDD, commit, lint)

Throughout the workflow, follow the loaded global guidelines.

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.