Run any Skill in Manus with one click

bordroom-lite-build-runner

Stars4

Forks0

UpdatedJune 6, 2026 at 04:41

Low-token bord.room V4.1 feature-slice delivery. Use for normal complete-dev implementation where the SQL backlog remains canonical but full traceability/prepush gates are reserved for checkpoints.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

zreed3

zreed3/agentic-development-platform

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	bordroom-lite-build-runner
description	Low-token bord.room V4.1 feature-slice delivery. Use for normal complete-dev implementation where the SQL backlog remains canonical but full traceability/prepush gates are reserved for checkpoints.

bord.room Lite Build Runner

Use this skill for day-to-day V4.1 implementation.

Default Loop

Plan
- Query the SQL backlog.
- Generate one bounded packet:
```
pnpm context:lite -- --feature S08
```
- Name the exact feature slice, routes/contracts, and files in scope.
Design
- Decide tenant/business scope, RBAC, entitlement, page-state behavior, and negative-test seams before editing.
- Do not invent product policy; use V4.1 docs and SQL rows.
Build
- Edit only scoped implementation files and directly related tests.
- Avoid generated docs until the slice is stable.
- Keep SQL backlog rows as the execution source; do not create parallel task lists.
Test
- Run targeted tests/checks first.
- Record failed commands once:
```
pnpm backlog:fail -- --item S08-TEST-01 --summary "Targeted check failed" --evidence "pnpm test -- ..."
```
- Record one consolidated verification when the same evidence covers multiple tasks, tests, use cases, or criteria.

Checkpoint Gates

Run full gates only at feature completion, release checkpoints, process/tooling changes, or before push:

pnpm ci:traceability
pnpm dev:prepush

During implementation, prefer:

pnpm lite:check
pnpm test -- <focused-test>
pnpm --filter <package> typecheck
pnpm db:validate-migrations

Use the DB/migration/security checks only when the slice touches those boundaries.

More from this repository

same repository

adg-backlog-decompose

zreed3/agentic-development-platform

Decompose a feature or intent into small, context-bound backlog items in the SQL backlog, for a planning model (Opus or Sonnet). Use before a swarm of workers: turn one feature into tightly scoped, logged items, each with a write scope and a context profile, so cheaper sub-agents can each work one item in isolation and total token use drops.

2026-06-154

adg-backlog-swarm

zreed3/agentic-development-platform

Orchestrate a context-bound, backlog-logged multi-agent swarm to cut token use. Use to run a feature as a planner (Opus or Sonnet) that logs small backlog items, then cheaper workers (Sonnet or Haiku) that each implement one item under its bounded context packet, while the parent keeps integration, the SQL backlog, the audit log, and verification.

2026-06-154

adg-evidence-curator

zreed3/agentic-development-platform

Select, record, and validate ADG evidence. Use when choosing targeted checks, recording failed commands, linking tests to requirements, writing audit events, registering advisory gaps, or preparing feature/release evidence.

2026-06-154

adg-feature-elicitation

zreed3/agentic-development-platform

Elicit generic ADG feature intent into a normalized requirements graph. Use when naming a feature, defining how it fits the platform, deriving RBAC-aligned stories and use cases, or creating success, anti-success, scenario, and gap evidence in config/agentic/elicitation.json.

2026-06-154

adg-item-worker

zreed3/agentic-development-platform

Work a single backlog item under a bounded context packet, for a context-cheap sub-agent (Sonnet or Haiku). Use when an orchestrator hands you one item id to implement in isolation: claim it, load only its context:item packet, edit only its write scope, record evidence, and complete it. Keeps token use low and work traceable.

2026-06-154

adg-quick-ui-fix

zreed3/agentic-development-platform

Use for small UI, copy, docs, styling, or visual polish fixes that should avoid full governance unless risk increases.

2026-06-154

name	bordroom-lite-build-runner
description	Low-token bord.room V4.1 feature-slice delivery. Use for normal complete-dev implementation where the SQL backlog remains canonical but full traceability/prepush gates are reserved for checkpoints.

bord.room Lite Build Runner

Use this skill for day-to-day V4.1 implementation.

Default Loop

Plan
- Query the SQL backlog.
- Generate one bounded packet:
```
pnpm context:lite -- --feature S08
```
- Name the exact feature slice, routes/contracts, and files in scope.
Design
- Decide tenant/business scope, RBAC, entitlement, page-state behavior, and negative-test seams before editing.
- Do not invent product policy; use V4.1 docs and SQL rows.
Build
- Edit only scoped implementation files and directly related tests.
- Avoid generated docs until the slice is stable.
- Keep SQL backlog rows as the execution source; do not create parallel task lists.
Test
- Run targeted tests/checks first.
- Record failed commands once:
```
pnpm backlog:fail -- --item S08-TEST-01 --summary "Targeted check failed" --evidence "pnpm test -- ..."
```
- Record one consolidated verification when the same evidence covers multiple tasks, tests, use cases, or criteria.

Checkpoint Gates

Run full gates only at feature completion, release checkpoints, process/tooling changes, or before push:

pnpm ci:traceability
pnpm dev:prepush

During implementation, prefer:

pnpm lite:check
pnpm test -- <focused-test>
pnpm --filter <package> typecheck
pnpm db:validate-migrations

Use the DB/migration/security checks only when the slice touches those boundaries.