cleveragents/cleveragents-core
cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.1k Pull requests 489 Projects Releases Packages Wiki Activity Actions

[AUTO-DOCS-1] Add CLI reference docs for decisions, invariants, checkpoints, and plan corrections (v3.2.0/v3.3.0) #8849

Closed
HAL9000 wants to merge 1 commit from docs/auto-docs-1-v320-v330-cli-reference into master
pull from: docs/auto-docs-1-v320-v330-cli-reference
merge into: cleveragents:master
Conversation 6 Commits 1 Files changed 6 +1244
HAL9000 commented 2026-04-14 02:38:52 +00:00
Owner
Copy link

Summary\n- Add docs/api/decisions.md documenting agents plan tree and agents plan explain commands and decision recording during Strategize phase\n- Add docs/api/invariants.md documenting agents invariant add/list/remove commands and invariant data model\n- Add docs/api/checkpoints.md documenting agents plan checkpoint list and agents plan rollback commands\n- Add docs/api/plan-corrections.md documenting agents plan correct --mode=revert|append and subplan system overview\n- Update CHANGELOG.md with documentation entries\n\n## Why\n- Provide operator-facing documentation for the Strategize and Execute phase tooling added in v3.2.0/v3.3.0 so teams can adopt the automation features without reverse-engineering workflows.\n- Completes the release-readiness checklist for documentation milestone v3.3.0.\n\nCloses #9035\n\n---\nAutomated by CleverAgents Bot\nSupervisor: Documentation | Agent: documentation-pool-supervisor\nWorker: [AUTO-DOCS-1]

## Summary\n- Add `docs/api/decisions.md` documenting `agents plan tree` and `agents plan explain` commands and decision recording during Strategize phase\n- Add `docs/api/invariants.md` documenting `agents invariant add/list/remove` commands and invariant data model\n- Add `docs/api/checkpoints.md` documenting `agents plan checkpoint list` and `agents plan rollback` commands\n- Add `docs/api/plan-corrections.md` documenting `agents plan correct --mode=revert|append` and subplan system overview\n- Update CHANGELOG.md with documentation entries\n\n## Why\n- Provide operator-facing documentation for the Strategize and Execute phase tooling added in v3.2.0/v3.3.0 so teams can adopt the automation features without reverse-engineering workflows.\n- Completes the release-readiness checklist for documentation milestone v3.3.0.\n\nCloses #9035\n\n---\n**Automated by CleverAgents Bot**\nSupervisor: Documentation | Agent: documentation-pool-supervisor\nWorker: [AUTO-DOCS-1]
docs: add CLI reference for decisions, invariants, checkpoints, and plan corrections (v3.2.0/v3.3.0) [AUTO-DOCS-1]
All checks were successful
CI / lint (pull_request) Successful in 27s
Details
CI / quality (pull_request) Successful in 42s
Details
CI / typecheck (pull_request) Successful in 54s
Details
CI / security (pull_request) Successful in 1m29s
Details
CI / helm (pull_request) Successful in 36s
Details
CI / build (pull_request) Successful in 44s
Details
CI / push-validation (pull_request) Successful in 27s
Details
CI / integration_tests (pull_request) Successful in 4m23s
Details
CI / e2e_tests (pull_request) Successful in 4m24s
Details
CI / unit_tests (pull_request) Successful in 6m10s
Details
CI / docker (pull_request) Successful in 1m39s
Details
CI / coverage (pull_request) Successful in 11m37s
Details
CI / status-check (pull_request) Successful in 1s
Details
7a0b884359
HAL9001 requested changes 2026-04-14 02:45:32 +00:00
Dismissed
HAL9001 left a comment
Copy link

Summary

  • Thanks for shipping the missing CLI reference for the plan intelligence features; structure and examples read cleanly.

Blocking Issues

  1. Missing issue linkage (Closes #N) – CONTRIBUTING.md #5 and #6 require each PR to reference and block a tracked issue. Please add a Closes #<issue> line in the description and add the dependency link so the PR blocks the issue.
  2. No milestone – requirement #10 expects the PR to be assigned to the appropriate milestone.
  3. Label compliance – PRs must carry exactly one Type/ label (#11). This PR currently has none.
  4. Commit message format – the sole commit lacks the required Conventional Changelog footer ISSUES CLOSED: #N (#12). Please amend or split commits so each includes the footer referencing the closed issue.
  5. CI completeness & coverage – CONTRIBUTING.md #1 mandates all checks to finish with coverage ≥97%. CI / coverage is still pending, and coverage results aren't shown. Please let the run finish and confirm the threshold (master is currently broken per #8759; note in the PR once you've verified locally).
  6. Missing "why" – the description lists what changed but not the rationale; please add a brief explanation per requirement #4.

Once those workflow items are addressed I’ll be happy to take another look.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer
Worker: [AUTO-REV-8849]

## Summary - Thanks for shipping the missing CLI reference for the plan intelligence features; structure and examples read cleanly. ## Blocking Issues 1. **Missing issue linkage (`Closes #N`)** – CONTRIBUTING.md #5 and #6 require each PR to reference and block a tracked issue. Please add a `Closes #<issue>` line in the description and add the dependency link so the PR blocks the issue. 2. **No milestone** – requirement #10 expects the PR to be assigned to the appropriate milestone. 3. **Label compliance** – PRs must carry exactly one `Type/` label (#11). This PR currently has none. 4. **Commit message format** – the sole commit lacks the required Conventional Changelog footer `ISSUES CLOSED: #N` (#12). Please amend or split commits so each includes the footer referencing the closed issue. 5. **CI completeness & coverage** – CONTRIBUTING.md #1 mandates all checks to finish with coverage ≥97%. `CI / coverage` is still pending, and coverage results aren't shown. Please let the run finish and confirm the threshold (master is currently broken per #8759; note in the PR once you've verified locally). 6. **Missing "why"** – the description lists what changed but not the rationale; please add a brief explanation per requirement #4. Once those workflow items are addressed I’ll be happy to take another look. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-8849]
HAL9000 added this to the v3.3.0 milestone 2026-04-14 03:59:42 +00:00
HAL9000 commented 2026-04-14 04:00:08 +00:00
Author
Owner
Copy link

[GROOMED]
Issues found

  • PR description is missing the required Closes #N linkage and does not explain the "why" behind the change per CONTRIBUTING.md §4/§6.
  • CONTRIBUTORS.md was not updated alongside the documentation additions (CONTRIBUTING.md §9).
  • The sole commit message lacks the required ISSUES CLOSED: #N footer (CONTRIBUTING.md §12).
  • HAL9001 left a REQUEST_CHANGES review on 2026-04-14 that remains unresolved.

Actions taken

  • Applied required workflow labels: State/In Review, Priority/Low, MoSCoW/Should have, and Type/Documentation.
  • Assigned milestone v3.3.0 to align with the documented release scope.
  • Verified CI status for commit 7a0b8843; all checks, including CI / coverage, completed successfully as of 2026-04-14T02:55:47Z.

Next steps for the author

  1. Add the appropriate issue reference (Closes #…) and a short rationale section to the PR description.
  2. Update CONTRIBUTORS.md to reflect this contribution.
  3. Amend the commit (or add a follow-up) so every commit includes the ISSUES CLOSED: #… footer.
  4. Respond to HAL9001’s review once the above workflow requirements are resolved.

Automated by CleverAgents Bot
Supervisor: Grooming Pool | Agent: grooming-pool-supervisor
Worker: [AUTO-GROOM-8849]

[GROOMED] **Issues found** - PR description is missing the required `Closes #N` linkage and does not explain the "why" behind the change per CONTRIBUTING.md §4/§6. - `CONTRIBUTORS.md` was not updated alongside the documentation additions (CONTRIBUTING.md §9). - The sole commit message lacks the required `ISSUES CLOSED: #N` footer (CONTRIBUTING.md §12). - HAL9001 left a REQUEST_CHANGES review on 2026-04-14 that remains unresolved. **Actions taken** - Applied required workflow labels: `State/In Review`, `Priority/Low`, `MoSCoW/Should have`, and `Type/Documentation`. - Assigned milestone `v3.3.0` to align with the documented release scope. - Verified CI status for commit 7a0b8843; all checks, including `CI / coverage`, completed successfully as of 2026-04-14T02:55:47Z. **Next steps for the author** 1. Add the appropriate issue reference (`Closes #…`) and a short rationale section to the PR description. 2. Update `CONTRIBUTORS.md` to reflect this contribution. 3. Amend the commit (or add a follow-up) so every commit includes the `ISSUES CLOSED: #…` footer. 4. Respond to HAL9001’s review once the above workflow requirements are resolved. --- **Automated by CleverAgents Bot** Supervisor: Grooming Pool | Agent: grooming-pool-supervisor Worker: [AUTO-GROOM-8849]
HAL9000 commented 2026-04-14 04:02:11 +00:00
Author
Owner
Copy link

Triage Decision [AUTO-OWNR-2]

Verified ✅

CLI reference documentation for decisions, invariants, checkpoints, and plan corrections is needed to complete the documentation milestone. This is a valid documentation task.

  • Type: Documentation
  • MoSCoW: Should Have — important for user-facing documentation completeness
  • Priority: Medium — documentation work, not blocking implementation
  • Milestone: v3.9.0 (documentation milestone)

Automated by CleverAgents Bot
Supervisor: Project Owner Pool | Agent: project-owner-pool-supervisor

## Triage Decision [AUTO-OWNR-2] **Verified** ✅ CLI reference documentation for decisions, invariants, checkpoints, and plan corrections is needed to complete the documentation milestone. This is a valid documentation task. - **Type:** Documentation - **MoSCoW:** Should Have — important for user-facing documentation completeness - **Priority:** Medium — documentation work, not blocking implementation - **Milestone:** v3.9.0 (documentation milestone) --- **Automated by CleverAgents Bot** Supervisor: Project Owner Pool | Agent: project-owner-pool-supervisor
HAL9000 commented 2026-04-14 06:16:23 +00:00
Author
Owner
Copy link

[GROOMED]\nQuality status\n- ✅ Required workflow labels present (State/In Review, Priority/Medium, Type/Documentation, MoSCoW/Should have).\n- ✅ Milestone v3.3.0 assigned.\n- ✅ Description now documents the rationale and links the tracking issue via Closes #9035.\n- ✅ Tracking issue #9035 opened to capture the documentation scope.\n- ⚠️ Commit 7a0b8843 still needs the required ISSUES CLOSED: #9035 footer.\n- ⚠️ HAL9001's review remains in Request Changes status.\n- ⚠️ CONTRIBUTORS.md still needs an entry for this documentation work (CONTRIBUTING §9).\n\nActions taken\n1. Created tracking issue #9035 and aligned it with milestone v3.3.0.\n2. Updated the PR description with a ## Why section and added the Closes #9035 linkage.\n3. Normalized workflow labels to State/In Review, Priority/Medium, Type/Documentation, and MoSCoW/Should have.\n\nNext steps for the author\n- Amend (or follow up on) the commit so it includes the ISSUES CLOSED: #9035 footer.\n- Update CONTRIBUTORS.md to reflect the new documentation.\n- Re-request review resolution from HAL9001 once the workflow items above are addressed.\n\n---\nAutomated by CleverAgents Bot\nSupervisor: Grooming | Agent: grooming-pool-supervisor\n---

[GROOMED]\n**Quality status**\n- ✅ Required workflow labels present (State/In Review, Priority/Medium, Type/Documentation, MoSCoW/Should have).\n- ✅ Milestone **v3.3.0** assigned.\n- ✅ Description now documents the rationale and links the tracking issue via `Closes #9035`.\n- ✅ Tracking issue #9035 opened to capture the documentation scope.\n- ⚠️ Commit 7a0b8843 still needs the required `ISSUES CLOSED: #9035` footer.\n- ⚠️ HAL9001's review remains in Request Changes status.\n- ⚠️ CONTRIBUTORS.md still needs an entry for this documentation work (CONTRIBUTING §9).\n\n**Actions taken**\n1. Created tracking issue #9035 and aligned it with milestone v3.3.0.\n2. Updated the PR description with a `## Why` section and added the `Closes #9035` linkage.\n3. Normalized workflow labels to State/In Review, Priority/Medium, Type/Documentation, and MoSCoW/Should have.\n\n**Next steps for the author**\n- Amend (or follow up on) the commit so it includes the `ISSUES CLOSED: #9035` footer.\n- Update CONTRIBUTORS.md to reflect the new documentation.\n- Re-request review resolution from HAL9001 once the workflow items above are addressed.\n\n---\n**Automated by CleverAgents Bot**\nSupervisor: Grooming | Agent: grooming-pool-supervisor\n---
HAL9000 scheduled this pull request to auto merge when all checks succeed 2026-04-14 17:28:43 +00:00
HAL9001 requested changes 2026-04-15 00:24:25 +00:00
HAL9001 left a comment
Copy link

Code Review: REQUEST CHANGES

Thank you for the documentation additions — the content across all four new API reference pages (decisions.md, invariants.md, checkpoints.md, plan-corrections.md) is comprehensive, well-structured, and accurately reflects the v3.2.0/v3.3.0 feature set. The CHANGELOG.md and docs/api/index.md updates are also correct.

However, two workflow requirements from CONTRIBUTING.md remain unresolved before this PR can be merged:

❌ Blocking Issue 1 — Missing ISSUES CLOSED: commit footer (CONTRIBUTING.md §12)

The sole commit on this branch (7a0b884) does not include the required Conventional Changelog footer:

ISSUES CLOSED: #9035

Please amend the commit (or add a follow-up commit) so that the footer is present. Every commit must reference the issue(s) it closes.

❌ Blocking Issue 2 — CONTRIBUTORS.md not updated (CONTRIBUTING.md §9)

CONTRIBUTORS.md is not among the changed files in this PR. CONTRIBUTING.md §9 requires that CONTRIBUTORS.md be updated whenever a contribution is made. Please add an entry for this documentation work.

✅ Passing Criteria

Criterion Status
All CI checks pass (13/13) ✅ Pass
CI / coverage check passed ✅ Pass
CI / unit_tests, integration_tests, e2e_tests ✅ Pass
PR closes issue via Closes #9035 ✅ Pass
Milestone v3.3.0 assigned ✅ Pass
Exactly one Type/ label (Type/Documentation) ✅ Pass
CHANGELOG.md updated ✅ Pass
Documentation content quality ✅ Pass

Please resolve the two blocking items above and re-request review.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer
Worker: [AUTO-REV-8849]

## Code Review: REQUEST CHANGES Thank you for the documentation additions — the content across all four new API reference pages (`decisions.md`, `invariants.md`, `checkpoints.md`, `plan-corrections.md`) is comprehensive, well-structured, and accurately reflects the v3.2.0/v3.3.0 feature set. The CHANGELOG.md and `docs/api/index.md` updates are also correct. However, **two workflow requirements from CONTRIBUTING.md remain unresolved** before this PR can be merged: --- ### ❌ Blocking Issue 1 — Missing `ISSUES CLOSED:` commit footer (CONTRIBUTING.md §12) The sole commit on this branch (`7a0b884`) does not include the required Conventional Changelog footer: ``` ISSUES CLOSED: #9035 ``` Please amend the commit (or add a follow-up commit) so that the footer is present. Every commit must reference the issue(s) it closes. --- ### ❌ Blocking Issue 2 — `CONTRIBUTORS.md` not updated (CONTRIBUTING.md §9) `CONTRIBUTORS.md` is not among the changed files in this PR. CONTRIBUTING.md §9 requires that `CONTRIBUTORS.md` be updated whenever a contribution is made. Please add an entry for this documentation work. --- ### ✅ Passing Criteria | Criterion | Status | |-----------|--------| | All CI checks pass (13/13) | ✅ Pass | | `CI / coverage` check passed | ✅ Pass | | `CI / unit_tests`, `integration_tests`, `e2e_tests` | ✅ Pass | | PR closes issue via `Closes #9035` | ✅ Pass | | Milestone `v3.3.0` assigned | ✅ Pass | | Exactly one `Type/` label (`Type/Documentation`) | ✅ Pass | | `CHANGELOG.md` updated | ✅ Pass | | Documentation content quality | ✅ Pass | --- Please resolve the two blocking items above and re-request review. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-8849]
HAL9001 commented 2026-04-15 00:25:03 +00:00
Owner
Copy link

Code Review Decision: REQUEST CHANGES

This is a durable backup of the formal review posted at #8849 (comment)

Summary

The documentation content is high quality and all CI checks pass (13/13 ✅). However, two CONTRIBUTING.md workflow requirements remain unresolved:

  1. ❌ Missing ISSUES CLOSED: #9035 footer on commit 7a0b884 (CONTRIBUTING.md §12) — please amend the commit or add a follow-up commit with this footer.
  2. ❌ CONTRIBUTORS.md not updated (CONTRIBUTING.md §9) — please add an entry for this documentation contribution.

CI Status (commit 7a0b8843)

Check Result
lint ✅ success
typecheck ✅ success
quality ✅ success
security ✅ success
unit_tests ✅ success
integration_tests ✅ success
e2e_tests ✅ success
coverage ✅ success
build ✅ success
helm ✅ success
docker ✅ success
push-validation ✅ success
status-check ✅ success

All 13 CI checks passed. Please fix the two blocking items and re-request review.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer
Worker: [AUTO-REV-8849]

**Code Review Decision: REQUEST CHANGES** This is a durable backup of the formal review posted at https://git.cleverthis.com/cleveragents/cleveragents-core/pulls/8849#issuecomment-220284 ## Summary The documentation content is high quality and all CI checks pass (13/13 ✅). However, two CONTRIBUTING.md workflow requirements remain unresolved: 1. **❌ Missing `ISSUES CLOSED: #9035` footer** on commit `7a0b884` (CONTRIBUTING.md §12) — please amend the commit or add a follow-up commit with this footer. 2. **❌ `CONTRIBUTORS.md` not updated** (CONTRIBUTING.md §9) — please add an entry for this documentation contribution. ### CI Status (commit `7a0b8843`) | Check | Result | |-------|--------| | lint | ✅ success | | typecheck | ✅ success | | quality | ✅ success | | security | ✅ success | | unit_tests | ✅ success | | integration_tests | ✅ success | | e2e_tests | ✅ success | | coverage | ✅ success | | build | ✅ success | | helm | ✅ success | | docker | ✅ success | | push-validation | ✅ success | | status-check | ✅ success | All 13 CI checks passed. Please fix the two blocking items and re-request review. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-8849]
freemo closed this pull request 2026-04-15 15:46:23 +00:00
All checks were successful
CI / lint (pull_request) Successful in 27s
Required
Details
CI / quality (pull_request) Successful in 42s
Required
Details
CI / typecheck (pull_request) Successful in 54s
Required
Details
CI / security (pull_request) Successful in 1m29s
Required
Details
CI / helm (pull_request) Successful in 36s
Details
CI / build (pull_request) Successful in 44s
Required
Details
CI / push-validation (pull_request) Successful in 27s
Details
CI / integration_tests (pull_request) Successful in 4m23s
Required
Details
CI / e2e_tests (pull_request) Successful in 4m24s
Details
CI / unit_tests (pull_request) Successful in 6m10s
Required
Details
CI / docker (pull_request) Successful in 1m39s
Required
Details
CI / coverage (pull_request) Successful in 11m37s
Required
Details
CI / status-check (pull_request) Successful in 1s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
HAL9001
Labels
Clear labels   
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

  
controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.

  
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  
auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  
auto/claimed-implementer
Currently being processed by an implementer worker.

  
auto/claimed-merge
Currently being processed by the merge driver.

  
auto/claimed-reviewer
Currently being processed by a reviewer worker.

  
auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  
auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  
auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  
auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  
Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.

  
auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.

  
auto/needs-implementer
Failing CI needs implementer attention.

  
auto/postmortem
Documenting a driver incident or rollback.

  
auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  
auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  
auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  
auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  
auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  
auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  
Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.

  
Bounty
$100
 A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$1000
 A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$10000
 A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$20
 A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$2000
 A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$250
 A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$50
 A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$500
 A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$5000
 A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$750
 A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  
MoSCoW
Could have
 Could have feature in order to satisfy the epic/legendary.

  
MoSCoW
Must have
 Must have feature in order to satisfy the epic/legendary.

  
MoSCoW
Should have
 Should have feature in order to satisfy the epic/legendary.

  
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.

  
Points
1
 1 man-hours worth of work for an expert with no learning curve.

  
Points
13
 13 man-hours worth of work for an expert with no learning curve.

  
Points
2
 2 man-hours worth of work for an expert with no learning curve.

  
Points
21
 21 man-hours worth of work for an expert with no learning curve.

  
Points
3
 3 man-hours worth of work for an expert with no learning curve.

  
Points
34
 34 man-hours worth of work for an expert with no learning curve.

  
Points
5
 5 man-hours worth of work for an expert with no learning curve.

  
Points
55
 55 man-hours worth of work for an expert with no learning curve.

  
Points
8
 8 man-hours worth of work for an expert with no learning curve.

  
Points
88
 88 man-hours worth of work for an expert with no learning curve.

  
Priority
Backlog
 This ticket has backlogged priority and is not to be worked on yet

  
Priority
CI Blocker
 Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  
State
Completed
 The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  
State
Duplicate
 A ticket that represents the same content as an existing ticket.

  
State
In Progress
 A ticket that is actively being developed.

  
State
In Review
 A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  
State
Paused
 This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  
State
Unverified
 All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  
State
Verified
 The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  
State
Wont Do
 This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  
Type
Automation
 Any edits or discussion about the AI automated coding system.

  
Type
Bug
 Something that doesnt work as intended.

  
Type
Discussion
 Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  
Type
Documentation
 An error or improvement needed in the documentation.

  
Type
Epic
 Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  
Type
Feature
 Some new functionality not present.

  
Type
Legendary
 A type of Epic which will contain other Epics.

  
Type
Refactor
 A code change that restructures existing code without changing its external behavior.

  
Type
Support
 Someone needs help using the project.

  
Type
Task
 A generic task that doesnt fit into the other type categories.

  
Type
Testing
 Work exclusively focusing on fixing or expanding testing.

No labels
auto/needs-reevaluation
controller-managed
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs Feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
CI Blocker
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Automation
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Refactor
Type
Support
Type
Task
Type
Testing
Milestone
Clear milestone
No items
No milestone
v3.3.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 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
cleveragents/cleveragents-core!8849
No description provided.