菜单
Agent artifact placement conventions. Use when creating plans, tasks, research, reviews, brainstorms, or any agent-generated files. Ensures artifacts go to docs/.claude/ (gitignored) instead of polluting the repo.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Multi-agent consensus code review with adaptive budgets, complexity-aware agent selection, multiple consensus protocols (Approval/Veto, AAD, CI, Supermajority), cross-agent coverage tracking, context-folding isolation, and progressive summarization. Use when reviewing PRs, directories, or code changes.
Use when creating new repositories, reviewing existing repos for compliance, or enforcing repository naming, structure, documentation, and security standards. Applies to all fyrsmithlabs projects.
Use when releasing a new version of a fyrsmithlabs plugin. Automates version bumping across all manifests (plugin.json, marketplace.json, CLAUDE.md), validates counts match disk, runs plugin-validator, creates git tag and GitHub release. Say "release the plugin", "bump version", "create a release".
This skill should be used when the user asks to "test opa", "opa test", "test rego", "write rego tests", "policy coverage", "conftest verify", "mock opa", or mentions `_test.rego` files. Provides OPA testing framework guidance including unit tests, mocking, coverage, and Conftest patterns.
This skill should be used when the user asks about "opa cli", "opa eval", "opa build", "opa check", "opa fmt", "regal lint", "opa bundle", "opa bench", "opa run", or mentions OPA tooling, CI/CD pipeline integration for OPA, or Rego linting. Provides OPA CLI and ecosystem tooling reference.
This skill should be used when the user asks about "kubernetes policy", "gatekeeper", "constraint template", "terraform policy", "conftest", "terraform compliance", "docker policy", "dockerfile policy", "envoy authz", "envoy authorization", "service mesh policy", "cloud policy", "aws policy rego", "azure policy rego", "gcp policy rego", or mentions writing OPA policies for a specific platform. Provides platform-specific Rego patterns and input schemas.
| name | agent-artifacts |
| description | Agent artifact placement conventions. Use when creating plans, tasks, research, reviews, brainstorms, or any agent-generated files. Ensures artifacts go to docs/.claude/ (gitignored) instead of polluting the repo. |
Agent-generated files (plans, tasks, research, reviews, orchestration output) MUST go to docs/.claude/, never the repo root. This directory is gitignored per git-repo-standards.
docs/.claude/
├── tasks/ # Todo lists, checklists, work tracking
├── plans/ # Implementation plans, design docs, architecture
├── research/ # Research results, analysis, findings
├── reviews/ # Consensus review reports, audit results
├── orchestration/ # Orchestration state, dispatch logs
└── brainstorms/ # Brainstorm sessions, ideation output
docs/.claude/<subdir>/ for generated files.claude/fs-dev-settings.json for project-specific overrides| Artifact Type | Directory | Examples |
|---|---|---|
| Plans | docs/.claude/plans/ | implementation plans, design approaches, architecture docs |
| Tasks | docs/.claude/tasks/ | todo lists, checklists, work items |
| Research | docs/.claude/research/ | technical research, competitive analysis, findings |
| Reviews | docs/.claude/reviews/ | consensus review reports, code audits |
| Orchestration | docs/.claude/orchestration/ | multi-agent dispatch state, execution logs |
| Brainstorms | docs/.claude/brainstorms/ | brainstorm transcripts, ideation notes |
Projects can customize via .claude/fs-dev-settings.json:
{
"agentArtifacts": {
"baseDir": "docs/.claude",
"allowedSubdirs": [
"tasks", "plans", "orchestration",
"research", "reviews", "brainstorms"
]
}
}
If the settings file doesn't exist, use the defaults above.
These belong at the repo root — do not redirect them:
CLAUDE.md, .claude.local.md — Claude Code configurationREADME.md, CHANGELOG.md, LICENSE — repo documentation.gitignore, .gitleaks.toml — repo configurationSECURITY.md, CONTRIBUTING.md, CODEOWNERS — repo standards