thanhnvandClaude Opus 4.8
36a4812ef3
Standard production layout: the OKR app (was nested under AINative_OKR_CASAN5/) is now
the repository root. No more wrapper directory.
- Promote AINative_OKR_CASAN5/* -> repo root (backend/ frontend/ packages/ apps/
.specify/ docs/ infra/ nginx/ scripts/ + configs). Merge tool dirs: .gitea (kept the
active deploy ci.yml, added harness-ci.yml + runbooks), .claude (agents/commands +
launch.json), .github moved up.
- Remove redundant: 00_SUBMISSION_PACKAGE, scattered root notes (FPT_CASAN_Full.md,
tu-tuong-casan.md, casan-tu-sinh..., casan_harness_assessment.md, source-review...,
README_CASAN5_REFINED.md), casan-next-plans/ and optimize-docs/ (competition/planning
artifacts — roadmap + design history preserved in git log / commit messages).
- Update all references to the old layout:
- .gitea/workflows/{ci,harness-ci}.yml, .github/workflows/{ci,deploy}.yml:
working-directory .; drop AINative_OKR_CASAN5/ prefix; .specify/{tests,scripts}
-> packages/casan-harness/... (.specify/logs state kept)
- .claude/launch.json, .gitea/*-runbook.md: path prefixes
- CLAUDE.md, README.md: docs/input -> apps/okr/domain/input
- policy-bundle.yaml: 8 policy paths -> packages/casan-harness/...; manifest re-signed
- secrets-scan.sh: fixture excludes -> new package/domain paths.
Full gate from the new root: PASS=64 FAIL=0 SKIP=3.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.8 KiB
description, allowed-tools
| description | allowed-tools |
|---|---|
| Run the full AI-SDLC pipeline end-to-end (fully autonomous, no pauses) | Agent, Read, Write, Edit, Bash, Glob, Grep, TodoWrite, WebFetch, WebSearch |
⚠️ MANDATORY: You MUST spawn the okr.bossbuiltin sub-agent via the Agent tool.
DO NOT implement anything yourself. DO NOT skip to coding. DO NOT generate docs directly.
Your ONLY job in this turn: prepare structured arguments → call Agent tool → wait for completion.
Step 1 — Derive feature-id
Read docs/output/output_logs/ to list existing feature folders:
Get-ChildItem docs/output/output_logs/ -Directory | Select-Object Name
- If directory is empty or does not exist → use
okr-feat-001 - If folders exist → increment the highest number (e.g.,
okr-feat-003→okr-feat-004)
Do NOT reuse an existing feature-id unless the user explicitly says "resume" or "continue".
Step 2 — Spawn the Boss Agent via Agent tool
Call the Agent tool with:
subagent_type:"okr.bossbuiltin"prompt: the structured YAML block below followed by the feature description
feature-id: <derived-feature-id>
module-id: mod01
module-keyword: OKR
pipeline-context: docs/output/output_logs/<feature-id>/pipeline-context.yaml
mode: autonomous
language: Vietnamese
Feature description: $ARGUMENTS
Step 3 — Do nothing else
Wait for the Agent tool to return. The boss agent runs the full 13-step pipeline: SRS → BD → Spec → Clarify → Review → Plan → Review → DD → Test Cases → Tasks → Implement → Code Review → QA → Launch
Do not intervene, generate code, or produce documents yourself. If Agent tool is unavailable, inform the user: "The okr.bossbuiltin agent is required. Please ensure it is registered in .claude/agents/okr.bossbuiltin.md."