Agent Scheduling & Capabilities

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
backend

Research direction

The issue names no files, tests, or entry points. First clarify the capability and scheduling requirements and expand the rationale and philosophy requested in the TODO; completion criteria are not defined yet.

Written by the indexing model from the issue text.

Description

It would be nice to also have agents be able to signal their capabilities (role on a project) and scheduling (which projects they have worked on, want to work on, etc.). This might close the gap when it comes to who works on what and in what capacity.

TO-DO: Expand on this, reason why, philosophy, etc.

Dominant language
TypeScript
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dOrgTech/AgentAvailability

All issues in dOrgTech/AgentAvailability

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.