メニュー
Capture the quality and standards baseline — linting, formatting, testing strategy, security, accessibility, performance budgets, documentation, and observability. Use when the project-builder agent is gathering quality/standards information.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Development workflow using an agent team (Analyst, Challenger, Developer, QA) to implement features, bug fixes, or refactors in a target project folder. Requires a PROJECT_BRIEF.md in the target folder; if missing, invokes project-builder first to generate one. Use BEFORE entering plan mode whenever the user asks for a code change in an external project. MUST be invoked whenever the user asks — even generically — to implement, build, add, fix, refactor, or "use the agents" / "use the team" on a target project, not only for fully detailed requests. If in doubt whether a request warrants this skill, prompt the user rather than silently proceeding solo.
Check whether the current Claude session was launched with --dangerously-skip-permissions. Run `ps aux`, find the claude process, and report yes/no via the command's exit code.
Generate a proper GitHub release description for a target project from the ACTUAL changes since the previous release tag — never by copying the prior release's notes. Produces a bullet-pointed "New features" section (each feature bullet up to 200 words) and a "Bugfixes" section (each bugfix bullet at most 50 words), with every bullet linking to the use case(s) it came from, then writes it to the release. Use whenever a release is cut for a target project (any release tag — a single `vX.Y.Z`, or per-component tags like `<component>-vX.Y.Z`), or standalone to (re)write the notes of an existing release.
Safely wait for and monitor any external-consequence outcome — CI runs, deploys, queue drains, container/service health, files appearing on disk — using the general "pre-flight the polled command, cap the loop, check exit code every iteration" pattern that prevents silent infinite stalls. Documents the reusable `wait_until` wrapper plus a concrete GitHub Actions instantiation (push / tag / PR-triggered runs, terminal-state field vocabularies, log-failed extraction) with every foot-gun that silently breaks polls. Use whenever a Claude run needs to wait for an asynchronous outcome before its next step.
Make a target project's own skills usable in the current session. Reads <TARGET_DIR>/.claude/skills/, symlinks each skill into ~/.claude/skills/ (so Claude Code hot-reloads them on the next turn), and records them in acquired-project-skills.json so the SessionEnd hook can remove them on exit. Invoke this at the START of working in any TARGET_DIR that ships its own .claude/skills/ — including from the project-builder, develop, revise-brief, and define-use-case entry points — or run it standalone to pull in one project's skills. Skips (never clobbers) any name already present in ~/.claude/skills/ or any name that matches a workspace skill.
Capture a single use case for a target project. Collects a free-form description from the user, produces a formalized version (summary, acceptance criteria, pitfalls), runs a clarifying-question loop, and saves the result as an incrementally-numbered Markdown file in the target project's `use-cases/` folder. After saving, offers to define another use case or continue to implementation via the `develop` skill. Use when the user wants to document what the project should do, before or instead of jumping into implementation.
| name | define-quality-standards |
| description | Capture the quality and standards baseline — linting, formatting, testing strategy, security, accessibility, performance budgets, documentation, and observability. Use when the project-builder agent is gathering quality/standards information. |
Decide what "good" means for this project up-front so the scaffold can include the right guardrails from day one.
profile-* skills in the session workspace should this project follow? List skill names by exact name (e.g., profile-java-database-access). Leave empty if none apply. If the user is unsure, glob <SESSION_DIR>/.claude/skills/profile-*/SKILL.md and show the names plus their description lines so the user can pick.Use AskUserQuestion where multiple choice fits.
npm audit, pip-audit, cargo audit), Dependabot or Renovate, Snyk, Semgrep, Trivy (containers), explicit threat-model document.style_guide (string)linters_formatters (list per language)testing ({levels, coverage_target, frameworks})security (list)accessibility_target (string)performance_budgets (list)documentation (string)observability (string)profiles (list of profile skill names — possibly empty)Write two top-level sections to PROJECT_BRIEF.md, in this order:
## Quality & Standards — captures the answers to questions 1–9 above. Replace any prior ## Quality & Standards section when re-run.## Profiles — one profile skill name per line, exactly as they appear in .claude/skills/. Write None on a single line if the list is empty. Replace any prior ## Profiles section when re-run.The ## Profiles section is a separate top-level heading (not a subsection) because every role agent reads it independently during the develop workflow.
Update these YAML frontmatter fields (see CLAUDE.md for the full schema). Leave every other field untouched:
test.framework — the primary test framework (e.g., junit, spock, pytest, vitest, jest, go test)test.levels — list of levels the project commits to (e.g., [unit, integration], [unit, integration, e2e])test.coverage_target — the stated target (e.g., 80%, none)profiles — list of profile skill names, exactly as they appear in .claude/skills/. Must be identical to the names written in the ## Profiles prose section; keep them in sync.