tfks/fjx
tfks/fjx
4
0
Fork 0
Code Issues 8 Pull requests Projects Releases Packages Wiki Activity Actions

Support an /assign USER PM command #32

New issue
Closed
opened 2026-06-23 13:24:20 +00:00 by erik · 3 comments
erik commented 2026-06-23 13:24:20 +00:00
Owner
Copy link

Since forgejo does not support /assign, have PM handle these. NOTE: the @ prefix for USER can be optional: @agent-dev and agent-dev must both be supported.

Since forgejo does not support `/assign`, have PM handle these. NOTE: the `@` prefix for USER can be optional: @agent-dev and agent-dev must both be supported.
agent-pm commented 2026-06-23 13:27:45 +00:00
Member
Copy link

Brief — Developer

Phase: simple. Run fjx dev prompt simple for the cycle protocol.

<!-- pm:brief:dev --> # Brief — Developer **Phase:** simple. Run `fjx dev prompt simple` for the cycle protocol.
agent-pm commented 2026-06-23 13:27:46 +00:00
Member
Copy link

Ledger for: agent-pm

Status: closed @ 2026-06-23T16:10:44.852Z
Briefs:

Activity

  1. i32/closed : applied

(PM manages this ledger; agent section unused)

<!-- agent-pm:ledger --> ## Ledger for: agent-pm Status: closed @ 2026-06-23T16:10:44.852Z Briefs: - [dev](#issuecomment-2815) ### Activity 1. i32/closed : applied --- _(PM manages this ledger; agent section unused)_
agent-dev commented 2026-06-23 13:31:13 +00:00
Member
Copy link

Ledger for: agent-dev

Status: review @ 2026-06-23T13:35:21.792Z
Refs: #33

Tasks

  • Create issue branch from origin/main.
  • Locate PM command parsing and assignment workflow.
  • Implement /assign USER with optional @ prefix.
  • Add focused test coverage.
  • Run validation.
  • Open PR.

Notes

  • Issue body is the spec for simple phase.
  • Planner now treats trusted /assign USER as an assignee dispatch; apply layer already writes assignees from plan.issueAssignee.
  • Commit: 4a8dd33 (chore: support pm assign command).
  • PR: #33.
  • Validation: deno test -A src/pm/plan.test.ts, just check, and just validate passed.
<!-- agent-dev:ledger --> ## Ledger for: agent-dev Status: review @ 2026-06-23T13:35:21.792Z Refs: #33 --- ## Tasks - [x] Create issue branch from origin/main. - [x] Locate PM command parsing and assignment workflow. - [x] Implement `/assign USER` with optional `@` prefix. - [x] Add focused test coverage. - [x] Run validation. - [x] Open PR. ## Notes - Issue body is the spec for simple phase. - Planner now treats trusted `/assign USER` as an assignee dispatch; apply layer already writes assignees from `plan.issueAssignee`. - Commit: `4a8dd33` (`chore: support pm assign command`). - PR: #33. - Validation: `deno test -A src/pm/plan.test.ts`, `just check`, and `just validate` passed.
agent-dev removed their assignment 2026-06-23 13:35:31 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v0.4.0
v0.3.9
v0.3.8
v0.3.7
v0.3.6
v0.3.5
v0.3.4
v0.3.3
v0.3.2
v0.3.1
v0.3.0
v0.2.6
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.1.4
v0.1.3
v0.1.2
v0.1.1
v0.1.0
Labels
Clear labels
  
agent
blocked
 Needs human intervention

  
agent
new
 Waiting triage by PM

  
agent
review
 Awaiting next phase

  
agent
working
 Agent is actively implementing

  
complexity
high
 High complexity - use more capable LLM

  
complexity
low
 Low complexity - use simpler LLM

  
priority
high
 High priority

  
priority
low
 Low priority

  
priority
medium
 Medium priority

  
risk
high
 High risk — strict QA, no auto-release

  
risk
low
 Low risk — standard flow

  
risk
medium
 Medium risk — standard QA

  
type
bug
 Bug fix

  
type
chore
 Maintenance, deps, tooling

  
type
feature
 New feature — spec required

  
type
security
 Security change — spec + strict QA required

No labels
agent
blocked
agent
new
agent
review
agent
working
complexity
high
complexity
low
priority
high
priority
low
priority
medium
risk
high
risk
low
risk
medium
type
bug
type
chore
type
feature
type
security
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
agent-pm
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
tfks/fjx#32
No description provided.