Skip to content

fleet skills: each repo's rules move back to its own repo, the cloud checklist skills state only differences, and dogfood-verification is updated (step 7) #35238

Open

Description

@objectstack-fleet

repo:objectstack#1 · os-warren · session_01JQwxbabAdcWyApSTGBYJNY

Filing gate: child of epic #35205, filed by seat 1. Ruling-ref: the maintainer said 「同意」 (2026-11-18 16:19Z) to the fleet skills review and its order of improvements (summary https://claude.ai/artifact/9TAontjAcKHUuajPPSKTGX; the three reports are in the project files under pm-orders/objectstack/skills-review-2026-11-18/). ⛔ Not a claim.

The order is one step, one PR, starting after the rule PR for #35207 merges: skill ratchet by bytes → #35215 (clear current values) → contradictions → slim entry files → lanes become seats plus epics (text → scripts → lane files) → split platform-readings → prose into scripts → each repo's rules back to its own repo, cloud skills and dogfood.

Blocked-by: #35235

What to do

Step 7. Ruled 2026-11-18 16:19–16:20Z: 「cloud 是不是应该放回cloud仓库」「包括 hotcrm 每个仓库的规则都在自己仓库」. objectstack's pm-dispatch keeps only the mechanisms every repo shares (the seat protocol, the label-write and first-touch scripts, the general part of the grade table). Each repo's own rules live in that repo: its area set, core features, grading details, seat charter, CI and verification, release aftercare.

  • The cloud lane rules already move to the cloud repository on cloud#4870 (docs/strategy/triage-rules.md beside core-functions.md). This card checks what is left: the cloud part of release-aftercare.md goes to cloud, lanes/hotcrm.md to hotcrm, lanes/mobile.md to mobile. One PR per repo, and objectstack keeps a one-line pointer for each.
  • The two cloud skills (checklist-author, checklist-test in the cloud repository) state only how they differ from the objectstack versions and point at those for the rest.
  • dogfood-verification is brought up to date with the current app and boot path.

The PRs in other repos follow those repos' rules for when they may land.

Done when

Every repo-specific rule lives in its own repo with a pointer from objectstack, the cloud skills carry only their differences, dogfood-verification matches today's app, and every touched repo's skill gates pass.

Activity

  1. objectstack-fleet commented on Nov 19, 2026

    @objectstack-fleet
    ContributorAuthor

    epic:#35205#1 · os-warren · session_01JQwxbYJqoPAoSpWTMpH1yq

    Blocked-by: #35237 → #35235 (same files) · 2026-11-19

    Was: Blocked-by: #35237 (scripts). Re-pointed to #35235: moving each repo's rules out of lanes/ edits the same files #35235 reorganises.

    Blocked-by: #35235

    Order: Warren, 2026-11-19 00:32Z 「可以拆的都同意。」 (item 6: the fleet skills clean-up chain becomes parallel; #35229 starts now). Rule: #35259 item 6 — fleet cards block each other only when they edit the same files. The new order is on #35205.


    Generated by Claude Code

  2. objectstack-fleet commented on Nov 19, 2026

    @objectstack-fleet
    ContributorAuthor

    repo:objectstack#1 · os-warren · session_01JQwxbYHmpLgwQvpwmbGvLL

    Grade: p2 → p1 — the maintainer's manual grade (no triage or seat moves it).

    Source: Warren, 2026-11-19 in the objectstack cloud os project thread: 04:51Z 「哪几个没做的,改到 p1」 — the not-yet-started fleet skill cards #35259, #35298, #35215, #35229–#35232 and #35234–#35238; 04:52Z 「不是让你做」 — relabel only. State label, assignee and Blocked-by lines are unchanged; nobody claims the card by this comment.

  3. added
    priority:p1High: required for production / M2
    and removed on Nov 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:fleetpm:blockedBlocked by another issue/PR — body carries Blocked-by: #Npriority:p1High: required for production / M2

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions