diff --git a/archdev/SKILL.md b/archdev/SKILL.md index d56f45e..7d1dd6e 100644 --- a/archdev/SKILL.md +++ b/archdev/SKILL.md @@ -1,6 +1,6 @@ --- name: archdev -description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks. +description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); generating, saving, and sharing live Ask dashboards (archdev ask); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks. --- # ArchDev @@ -139,6 +139,53 @@ subagents and agents you spawn. - PR reporting requires no local grading, annotations, or stop hold, including Factory and daemon sessions. Follow the host's publication ownership. +## Ask dashboards + +Use `archdev ask` when someone wants a live dashboard of their team's work, +PRs, risk, agents, or lessons. Run the CLI for them and return the view's URL; +they do not need to open the frontend to create it. Check `"$archdev" ask --help` +first: older releases do not have this command group. Do not upgrade without +approval. These commands need an ArchDev user login and the +`archdev_ask_views` feature flag; a 404 can mean Ask is not enabled, not that +a dashboard is missing. Hosted generation uses ArchDev's model sponsorship, +not the coding agent's local provider configuration. + +```sh +# Generate and save a personal live view; no Company Room post. +"$archdev" --json ask create "Show open PR risk grouped by repository" +# Inspect or revise a view using its returned art_… ID. +"$archdev" --json ask list +"$archdev" --json ask show +"$archdev" --json ask update "Group by author instead" +# Generate JSX without saving it or posting anything. +"$archdev" --json ask generate "Show agents that are stuck" +# Save supplied JSX without a model call (uses the Ask component kit). +"$archdev" --json ask create "Team progress" --title "Team progress" --code-file view.jsx +# Only with permission to share with the team: +"$archdev" --json ask create "Where is the risk?" --share --pin +"$archdev" --json ask share --pin +# Archive the personal saved view; shared tiles are not removed. +"$archdev" --json ask delete +``` + +`create` saves a personal artifact and returns `id` and `url`. `--title` +overrides the generated title; `--code-file` on `create` or `update` uses +supplied JSX instead of calling the model. On `generate`, `--code-file` +provides the current program for the model to revise. Use `--json` for +machine-readable output; do not mistake a provisional streamed program for +a completed generation. + +Sharing is a separate write: `create --share` or `share` posts the question +and a copy of its JSX to the Company Room's Ask board. `--pin` pins that new +tile (`create --pin` also requires `--share`). Ask permission before publishing +personal content to the team. Shared views run on each viewer's own live data +and permissions, not the author's login. Updating or deleting the personal +artifact does not update or delete earlier shared copies; sharing again +creates a new tile. If saving succeeds but sharing fails, keep the returned +artifact ID from the error and retry `ask share`, not `ask create`. +Inspect the Ask board before retrying an unconfirmed room write: a timeout +can happen after the post was accepted, and a new share can duplicate it. + ## Rule candidates from a session When a user asks to turn a correction into a repository rule, follow diff --git a/plugins/antigravity/skills/archdev/SKILL.md b/plugins/antigravity/skills/archdev/SKILL.md index d56f45e..7d1dd6e 100644 --- a/plugins/antigravity/skills/archdev/SKILL.md +++ b/plugins/antigravity/skills/archdev/SKILL.md @@ -1,6 +1,6 @@ --- name: archdev -description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks. +description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); generating, saving, and sharing live Ask dashboards (archdev ask); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks. --- # ArchDev @@ -139,6 +139,53 @@ subagents and agents you spawn. - PR reporting requires no local grading, annotations, or stop hold, including Factory and daemon sessions. Follow the host's publication ownership. +## Ask dashboards + +Use `archdev ask` when someone wants a live dashboard of their team's work, +PRs, risk, agents, or lessons. Run the CLI for them and return the view's URL; +they do not need to open the frontend to create it. Check `"$archdev" ask --help` +first: older releases do not have this command group. Do not upgrade without +approval. These commands need an ArchDev user login and the +`archdev_ask_views` feature flag; a 404 can mean Ask is not enabled, not that +a dashboard is missing. Hosted generation uses ArchDev's model sponsorship, +not the coding agent's local provider configuration. + +```sh +# Generate and save a personal live view; no Company Room post. +"$archdev" --json ask create "Show open PR risk grouped by repository" +# Inspect or revise a view using its returned art_… ID. +"$archdev" --json ask list +"$archdev" --json ask show +"$archdev" --json ask update "Group by author instead" +# Generate JSX without saving it or posting anything. +"$archdev" --json ask generate "Show agents that are stuck" +# Save supplied JSX without a model call (uses the Ask component kit). +"$archdev" --json ask create "Team progress" --title "Team progress" --code-file view.jsx +# Only with permission to share with the team: +"$archdev" --json ask create "Where is the risk?" --share --pin +"$archdev" --json ask share --pin +# Archive the personal saved view; shared tiles are not removed. +"$archdev" --json ask delete +``` + +`create` saves a personal artifact and returns `id` and `url`. `--title` +overrides the generated title; `--code-file` on `create` or `update` uses +supplied JSX instead of calling the model. On `generate`, `--code-file` +provides the current program for the model to revise. Use `--json` for +machine-readable output; do not mistake a provisional streamed program for +a completed generation. + +Sharing is a separate write: `create --share` or `share` posts the question +and a copy of its JSX to the Company Room's Ask board. `--pin` pins that new +tile (`create --pin` also requires `--share`). Ask permission before publishing +personal content to the team. Shared views run on each viewer's own live data +and permissions, not the author's login. Updating or deleting the personal +artifact does not update or delete earlier shared copies; sharing again +creates a new tile. If saving succeeds but sharing fails, keep the returned +artifact ID from the error and retry `ask share`, not `ask create`. +Inspect the Ask board before retrying an unconfirmed room write: a timeout +can happen after the post was accepted, and a new share can duplicate it. + ## Rule candidates from a session When a user asks to turn a correction into a repository rule, follow diff --git a/plugins/claude/skills/archdev/SKILL.md b/plugins/claude/skills/archdev/SKILL.md index d56f45e..7d1dd6e 100644 --- a/plugins/claude/skills/archdev/SKILL.md +++ b/plugins/claude/skills/archdev/SKILL.md @@ -1,6 +1,6 @@ --- name: archdev -description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks. +description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); generating, saving, and sharing live Ask dashboards (archdev ask); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks. --- # ArchDev @@ -139,6 +139,53 @@ subagents and agents you spawn. - PR reporting requires no local grading, annotations, or stop hold, including Factory and daemon sessions. Follow the host's publication ownership. +## Ask dashboards + +Use `archdev ask` when someone wants a live dashboard of their team's work, +PRs, risk, agents, or lessons. Run the CLI for them and return the view's URL; +they do not need to open the frontend to create it. Check `"$archdev" ask --help` +first: older releases do not have this command group. Do not upgrade without +approval. These commands need an ArchDev user login and the +`archdev_ask_views` feature flag; a 404 can mean Ask is not enabled, not that +a dashboard is missing. Hosted generation uses ArchDev's model sponsorship, +not the coding agent's local provider configuration. + +```sh +# Generate and save a personal live view; no Company Room post. +"$archdev" --json ask create "Show open PR risk grouped by repository" +# Inspect or revise a view using its returned art_… ID. +"$archdev" --json ask list +"$archdev" --json ask show +"$archdev" --json ask update "Group by author instead" +# Generate JSX without saving it or posting anything. +"$archdev" --json ask generate "Show agents that are stuck" +# Save supplied JSX without a model call (uses the Ask component kit). +"$archdev" --json ask create "Team progress" --title "Team progress" --code-file view.jsx +# Only with permission to share with the team: +"$archdev" --json ask create "Where is the risk?" --share --pin +"$archdev" --json ask share --pin +# Archive the personal saved view; shared tiles are not removed. +"$archdev" --json ask delete +``` + +`create` saves a personal artifact and returns `id` and `url`. `--title` +overrides the generated title; `--code-file` on `create` or `update` uses +supplied JSX instead of calling the model. On `generate`, `--code-file` +provides the current program for the model to revise. Use `--json` for +machine-readable output; do not mistake a provisional streamed program for +a completed generation. + +Sharing is a separate write: `create --share` or `share` posts the question +and a copy of its JSX to the Company Room's Ask board. `--pin` pins that new +tile (`create --pin` also requires `--share`). Ask permission before publishing +personal content to the team. Shared views run on each viewer's own live data +and permissions, not the author's login. Updating or deleting the personal +artifact does not update or delete earlier shared copies; sharing again +creates a new tile. If saving succeeds but sharing fails, keep the returned +artifact ID from the error and retry `ask share`, not `ask create`. +Inspect the Ask board before retrying an unconfirmed room write: a timeout +can happen after the post was accepted, and a new share can duplicate it. + ## Rule candidates from a session When a user asks to turn a correction into a repository rule, follow diff --git a/plugins/codex/skills/archdev/SKILL.md b/plugins/codex/skills/archdev/SKILL.md index d56f45e..7d1dd6e 100644 --- a/plugins/codex/skills/archdev/SKILL.md +++ b/plugins/codex/skills/archdev/SKILL.md @@ -1,6 +1,6 @@ --- name: archdev -description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks. +description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); generating, saving, and sharing live Ask dashboards (archdev ask); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks. --- # ArchDev @@ -139,6 +139,53 @@ subagents and agents you spawn. - PR reporting requires no local grading, annotations, or stop hold, including Factory and daemon sessions. Follow the host's publication ownership. +## Ask dashboards + +Use `archdev ask` when someone wants a live dashboard of their team's work, +PRs, risk, agents, or lessons. Run the CLI for them and return the view's URL; +they do not need to open the frontend to create it. Check `"$archdev" ask --help` +first: older releases do not have this command group. Do not upgrade without +approval. These commands need an ArchDev user login and the +`archdev_ask_views` feature flag; a 404 can mean Ask is not enabled, not that +a dashboard is missing. Hosted generation uses ArchDev's model sponsorship, +not the coding agent's local provider configuration. + +```sh +# Generate and save a personal live view; no Company Room post. +"$archdev" --json ask create "Show open PR risk grouped by repository" +# Inspect or revise a view using its returned art_… ID. +"$archdev" --json ask list +"$archdev" --json ask show +"$archdev" --json ask update "Group by author instead" +# Generate JSX without saving it or posting anything. +"$archdev" --json ask generate "Show agents that are stuck" +# Save supplied JSX without a model call (uses the Ask component kit). +"$archdev" --json ask create "Team progress" --title "Team progress" --code-file view.jsx +# Only with permission to share with the team: +"$archdev" --json ask create "Where is the risk?" --share --pin +"$archdev" --json ask share --pin +# Archive the personal saved view; shared tiles are not removed. +"$archdev" --json ask delete +``` + +`create` saves a personal artifact and returns `id` and `url`. `--title` +overrides the generated title; `--code-file` on `create` or `update` uses +supplied JSX instead of calling the model. On `generate`, `--code-file` +provides the current program for the model to revise. Use `--json` for +machine-readable output; do not mistake a provisional streamed program for +a completed generation. + +Sharing is a separate write: `create --share` or `share` posts the question +and a copy of its JSX to the Company Room's Ask board. `--pin` pins that new +tile (`create --pin` also requires `--share`). Ask permission before publishing +personal content to the team. Shared views run on each viewer's own live data +and permissions, not the author's login. Updating or deleting the personal +artifact does not update or delete earlier shared copies; sharing again +creates a new tile. If saving succeeds but sharing fails, keep the returned +artifact ID from the error and retry `ask share`, not `ask create`. +Inspect the Ask board before retrying an unconfirmed room write: a timeout +can happen after the post was accepted, and a new share can duplicate it. + ## Rule candidates from a session When a user asks to turn a correction into a repository rule, follow diff --git a/plugins/copilot/skills/archdev/SKILL.md b/plugins/copilot/skills/archdev/SKILL.md index d56f45e..7d1dd6e 100644 --- a/plugins/copilot/skills/archdev/SKILL.md +++ b/plugins/copilot/skills/archdev/SKILL.md @@ -1,6 +1,6 @@ --- name: archdev -description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks. +description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); generating, saving, and sharing live Ask dashboards (archdev ask); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks. --- # ArchDev @@ -139,6 +139,53 @@ subagents and agents you spawn. - PR reporting requires no local grading, annotations, or stop hold, including Factory and daemon sessions. Follow the host's publication ownership. +## Ask dashboards + +Use `archdev ask` when someone wants a live dashboard of their team's work, +PRs, risk, agents, or lessons. Run the CLI for them and return the view's URL; +they do not need to open the frontend to create it. Check `"$archdev" ask --help` +first: older releases do not have this command group. Do not upgrade without +approval. These commands need an ArchDev user login and the +`archdev_ask_views` feature flag; a 404 can mean Ask is not enabled, not that +a dashboard is missing. Hosted generation uses ArchDev's model sponsorship, +not the coding agent's local provider configuration. + +```sh +# Generate and save a personal live view; no Company Room post. +"$archdev" --json ask create "Show open PR risk grouped by repository" +# Inspect or revise a view using its returned art_… ID. +"$archdev" --json ask list +"$archdev" --json ask show +"$archdev" --json ask update "Group by author instead" +# Generate JSX without saving it or posting anything. +"$archdev" --json ask generate "Show agents that are stuck" +# Save supplied JSX without a model call (uses the Ask component kit). +"$archdev" --json ask create "Team progress" --title "Team progress" --code-file view.jsx +# Only with permission to share with the team: +"$archdev" --json ask create "Where is the risk?" --share --pin +"$archdev" --json ask share --pin +# Archive the personal saved view; shared tiles are not removed. +"$archdev" --json ask delete +``` + +`create` saves a personal artifact and returns `id` and `url`. `--title` +overrides the generated title; `--code-file` on `create` or `update` uses +supplied JSX instead of calling the model. On `generate`, `--code-file` +provides the current program for the model to revise. Use `--json` for +machine-readable output; do not mistake a provisional streamed program for +a completed generation. + +Sharing is a separate write: `create --share` or `share` posts the question +and a copy of its JSX to the Company Room's Ask board. `--pin` pins that new +tile (`create --pin` also requires `--share`). Ask permission before publishing +personal content to the team. Shared views run on each viewer's own live data +and permissions, not the author's login. Updating or deleting the personal +artifact does not update or delete earlier shared copies; sharing again +creates a new tile. If saving succeeds but sharing fails, keep the returned +artifact ID from the error and retry `ask share`, not `ask create`. +Inspect the Ask board before retrying an unconfirmed room write: a timeout +can happen after the post was accepted, and a new share can duplicate it. + ## Rule candidates from a session When a user asks to turn a correction into a repository rule, follow diff --git a/plugins/cursor/skills/archdev/SKILL.md b/plugins/cursor/skills/archdev/SKILL.md index d56f45e..7d1dd6e 100644 --- a/plugins/cursor/skills/archdev/SKILL.md +++ b/plugins/cursor/skills/archdev/SKILL.md @@ -1,6 +1,6 @@ --- name: archdev -description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks. +description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); generating, saving, and sharing live Ask dashboards (archdev ask); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks. --- # ArchDev @@ -139,6 +139,53 @@ subagents and agents you spawn. - PR reporting requires no local grading, annotations, or stop hold, including Factory and daemon sessions. Follow the host's publication ownership. +## Ask dashboards + +Use `archdev ask` when someone wants a live dashboard of their team's work, +PRs, risk, agents, or lessons. Run the CLI for them and return the view's URL; +they do not need to open the frontend to create it. Check `"$archdev" ask --help` +first: older releases do not have this command group. Do not upgrade without +approval. These commands need an ArchDev user login and the +`archdev_ask_views` feature flag; a 404 can mean Ask is not enabled, not that +a dashboard is missing. Hosted generation uses ArchDev's model sponsorship, +not the coding agent's local provider configuration. + +```sh +# Generate and save a personal live view; no Company Room post. +"$archdev" --json ask create "Show open PR risk grouped by repository" +# Inspect or revise a view using its returned art_… ID. +"$archdev" --json ask list +"$archdev" --json ask show +"$archdev" --json ask update "Group by author instead" +# Generate JSX without saving it or posting anything. +"$archdev" --json ask generate "Show agents that are stuck" +# Save supplied JSX without a model call (uses the Ask component kit). +"$archdev" --json ask create "Team progress" --title "Team progress" --code-file view.jsx +# Only with permission to share with the team: +"$archdev" --json ask create "Where is the risk?" --share --pin +"$archdev" --json ask share --pin +# Archive the personal saved view; shared tiles are not removed. +"$archdev" --json ask delete +``` + +`create` saves a personal artifact and returns `id` and `url`. `--title` +overrides the generated title; `--code-file` on `create` or `update` uses +supplied JSX instead of calling the model. On `generate`, `--code-file` +provides the current program for the model to revise. Use `--json` for +machine-readable output; do not mistake a provisional streamed program for +a completed generation. + +Sharing is a separate write: `create --share` or `share` posts the question +and a copy of its JSX to the Company Room's Ask board. `--pin` pins that new +tile (`create --pin` also requires `--share`). Ask permission before publishing +personal content to the team. Shared views run on each viewer's own live data +and permissions, not the author's login. Updating or deleting the personal +artifact does not update or delete earlier shared copies; sharing again +creates a new tile. If saving succeeds but sharing fails, keep the returned +artifact ID from the error and retry `ask share`, not `ask create`. +Inspect the Ask board before retrying an unconfirmed room write: a timeout +can happen after the post was accepted, and a new share can duplicate it. + ## Rule candidates from a session When a user asks to turn a correction into a repository rule, follow diff --git a/plugins/grok/skills/archdev/SKILL.md b/plugins/grok/skills/archdev/SKILL.md index d56f45e..7d1dd6e 100644 --- a/plugins/grok/skills/archdev/SKILL.md +++ b/plugins/grok/skills/archdev/SKILL.md @@ -1,6 +1,6 @@ --- name: archdev -description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks. +description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); generating, saving, and sharing live Ask dashboards (archdev ask); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks. --- # ArchDev @@ -139,6 +139,53 @@ subagents and agents you spawn. - PR reporting requires no local grading, annotations, or stop hold, including Factory and daemon sessions. Follow the host's publication ownership. +## Ask dashboards + +Use `archdev ask` when someone wants a live dashboard of their team's work, +PRs, risk, agents, or lessons. Run the CLI for them and return the view's URL; +they do not need to open the frontend to create it. Check `"$archdev" ask --help` +first: older releases do not have this command group. Do not upgrade without +approval. These commands need an ArchDev user login and the +`archdev_ask_views` feature flag; a 404 can mean Ask is not enabled, not that +a dashboard is missing. Hosted generation uses ArchDev's model sponsorship, +not the coding agent's local provider configuration. + +```sh +# Generate and save a personal live view; no Company Room post. +"$archdev" --json ask create "Show open PR risk grouped by repository" +# Inspect or revise a view using its returned art_… ID. +"$archdev" --json ask list +"$archdev" --json ask show +"$archdev" --json ask update "Group by author instead" +# Generate JSX without saving it or posting anything. +"$archdev" --json ask generate "Show agents that are stuck" +# Save supplied JSX without a model call (uses the Ask component kit). +"$archdev" --json ask create "Team progress" --title "Team progress" --code-file view.jsx +# Only with permission to share with the team: +"$archdev" --json ask create "Where is the risk?" --share --pin +"$archdev" --json ask share --pin +# Archive the personal saved view; shared tiles are not removed. +"$archdev" --json ask delete +``` + +`create` saves a personal artifact and returns `id` and `url`. `--title` +overrides the generated title; `--code-file` on `create` or `update` uses +supplied JSX instead of calling the model. On `generate`, `--code-file` +provides the current program for the model to revise. Use `--json` for +machine-readable output; do not mistake a provisional streamed program for +a completed generation. + +Sharing is a separate write: `create --share` or `share` posts the question +and a copy of its JSX to the Company Room's Ask board. `--pin` pins that new +tile (`create --pin` also requires `--share`). Ask permission before publishing +personal content to the team. Shared views run on each viewer's own live data +and permissions, not the author's login. Updating or deleting the personal +artifact does not update or delete earlier shared copies; sharing again +creates a new tile. If saving succeeds but sharing fails, keep the returned +artifact ID from the error and retry `ask share`, not `ask create`. +Inspect the Ask board before retrying an unconfirmed room write: a timeout +can happen after the post was accepted, and a new share can duplicate it. + ## Rule candidates from a session When a user asks to turn a correction into a repository rule, follow diff --git a/plugins/opencode/skills/archdev/SKILL.md b/plugins/opencode/skills/archdev/SKILL.md index d56f45e..7d1dd6e 100644 --- a/plugins/opencode/skills/archdev/SKILL.md +++ b/plugins/opencode/skills/archdev/SKILL.md @@ -1,6 +1,6 @@ --- name: archdev -description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks. +description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); generating, saving, and sharing live Ask dashboards (archdev ask); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks. --- # ArchDev @@ -139,6 +139,53 @@ subagents and agents you spawn. - PR reporting requires no local grading, annotations, or stop hold, including Factory and daemon sessions. Follow the host's publication ownership. +## Ask dashboards + +Use `archdev ask` when someone wants a live dashboard of their team's work, +PRs, risk, agents, or lessons. Run the CLI for them and return the view's URL; +they do not need to open the frontend to create it. Check `"$archdev" ask --help` +first: older releases do not have this command group. Do not upgrade without +approval. These commands need an ArchDev user login and the +`archdev_ask_views` feature flag; a 404 can mean Ask is not enabled, not that +a dashboard is missing. Hosted generation uses ArchDev's model sponsorship, +not the coding agent's local provider configuration. + +```sh +# Generate and save a personal live view; no Company Room post. +"$archdev" --json ask create "Show open PR risk grouped by repository" +# Inspect or revise a view using its returned art_… ID. +"$archdev" --json ask list +"$archdev" --json ask show +"$archdev" --json ask update "Group by author instead" +# Generate JSX without saving it or posting anything. +"$archdev" --json ask generate "Show agents that are stuck" +# Save supplied JSX without a model call (uses the Ask component kit). +"$archdev" --json ask create "Team progress" --title "Team progress" --code-file view.jsx +# Only with permission to share with the team: +"$archdev" --json ask create "Where is the risk?" --share --pin +"$archdev" --json ask share --pin +# Archive the personal saved view; shared tiles are not removed. +"$archdev" --json ask delete +``` + +`create` saves a personal artifact and returns `id` and `url`. `--title` +overrides the generated title; `--code-file` on `create` or `update` uses +supplied JSX instead of calling the model. On `generate`, `--code-file` +provides the current program for the model to revise. Use `--json` for +machine-readable output; do not mistake a provisional streamed program for +a completed generation. + +Sharing is a separate write: `create --share` or `share` posts the question +and a copy of its JSX to the Company Room's Ask board. `--pin` pins that new +tile (`create --pin` also requires `--share`). Ask permission before publishing +personal content to the team. Shared views run on each viewer's own live data +and permissions, not the author's login. Updating or deleting the personal +artifact does not update or delete earlier shared copies; sharing again +creates a new tile. If saving succeeds but sharing fails, keep the returned +artifact ID from the error and retry `ask share`, not `ask create`. +Inspect the Ask board before retrying an unconfirmed room write: a timeout +can happen after the post was accepted, and a new share can duplicate it. + ## Rule candidates from a session When a user asks to turn a correction into a repository rule, follow diff --git a/plugins/pi/skills/archdev/SKILL.md b/plugins/pi/skills/archdev/SKILL.md index d56f45e..7d1dd6e 100644 --- a/plugins/pi/skills/archdev/SKILL.md +++ b/plugins/pi/skills/archdev/SKILL.md @@ -1,6 +1,6 @@ --- name: archdev -description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks. +description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); generating, saving, and sharing live Ask dashboards (archdev ask); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks. --- # ArchDev @@ -139,6 +139,53 @@ subagents and agents you spawn. - PR reporting requires no local grading, annotations, or stop hold, including Factory and daemon sessions. Follow the host's publication ownership. +## Ask dashboards + +Use `archdev ask` when someone wants a live dashboard of their team's work, +PRs, risk, agents, or lessons. Run the CLI for them and return the view's URL; +they do not need to open the frontend to create it. Check `"$archdev" ask --help` +first: older releases do not have this command group. Do not upgrade without +approval. These commands need an ArchDev user login and the +`archdev_ask_views` feature flag; a 404 can mean Ask is not enabled, not that +a dashboard is missing. Hosted generation uses ArchDev's model sponsorship, +not the coding agent's local provider configuration. + +```sh +# Generate and save a personal live view; no Company Room post. +"$archdev" --json ask create "Show open PR risk grouped by repository" +# Inspect or revise a view using its returned art_… ID. +"$archdev" --json ask list +"$archdev" --json ask show +"$archdev" --json ask update "Group by author instead" +# Generate JSX without saving it or posting anything. +"$archdev" --json ask generate "Show agents that are stuck" +# Save supplied JSX without a model call (uses the Ask component kit). +"$archdev" --json ask create "Team progress" --title "Team progress" --code-file view.jsx +# Only with permission to share with the team: +"$archdev" --json ask create "Where is the risk?" --share --pin +"$archdev" --json ask share --pin +# Archive the personal saved view; shared tiles are not removed. +"$archdev" --json ask delete +``` + +`create` saves a personal artifact and returns `id` and `url`. `--title` +overrides the generated title; `--code-file` on `create` or `update` uses +supplied JSX instead of calling the model. On `generate`, `--code-file` +provides the current program for the model to revise. Use `--json` for +machine-readable output; do not mistake a provisional streamed program for +a completed generation. + +Sharing is a separate write: `create --share` or `share` posts the question +and a copy of its JSX to the Company Room's Ask board. `--pin` pins that new +tile (`create --pin` also requires `--share`). Ask permission before publishing +personal content to the team. Shared views run on each viewer's own live data +and permissions, not the author's login. Updating or deleting the personal +artifact does not update or delete earlier shared copies; sharing again +creates a new tile. If saving succeeds but sharing fails, keep the returned +artifact ID from the error and retry `ask share`, not `ask create`. +Inspect the Ask board before retrying an unconfirmed room write: a timeout +can happen after the post was accepted, and a new share can duplicate it. + ## Rule candidates from a session When a user asks to turn a correction into a repository rule, follow diff --git a/tools/plugin-gen/test/generate.test.ts b/tools/plugin-gen/test/generate.test.ts index cf76ce3..7ac1e79 100644 --- a/tools/plugin-gen/test/generate.test.ts +++ b/tools/plugin-gen/test/generate.test.ts @@ -120,6 +120,26 @@ describe("generation", () => { assert.match(NUDGE_TEXT.plan, /RISK_STEPS/); }); + test("Ask dashboards are discoverable and distinguish personal saves from team sharing", () => { + const skill = readFileSync(path.join(repoRoot, "archdev/SKILL.md"), "utf8"); + const ask = skill.split("## Ask dashboards\n")[1]?.split("\n## ")[0]; + assert.ok(ask, "Ask has agent-facing guidance in the core skill"); + assert.match(skill.split("---")[1]!, /live Ask dashboards \(archdev ask\)/); + for (const command of ["create", "generate", "list", "show", "update", "delete", "share"]) { + assert.ok(ask.includes(`ask ${command}`), `documents ask ${command}`); + } + assert.match(ask, /archdev_ask_views/); + assert.match(ask, /older releases do not have this command group/); + assert.match(ask, /no Company Room post/); + assert.match(ask, /Ask permission before publishing/); + assert.match(ask, /each viewer's own live data/); + assert.match(ask, /does not update or delete earlier shared copies/); + assert.match(ask, /retry `ask share`, not `ask create`/); + for (const harness of HARNESSES) { + assert.equal(byPath.get(`${ADAPTERS[harness].root}/skills/archdev/SKILL.md`)?.content.toString("utf8"), skill); + } + }); + test("review queries expose exact-head risk and scope without making reporting wait", () => { const skill = readFileSync(path.join(repoRoot, "archdev/SKILL.md"), "utf8"); assert.match(skill, /references\/monitor\.md#read-pr-risk-scope-and-rules/);