boundary-policy-classification-by-role
Classify artifacts as durable vs transient by their functional role rather than directory path, using multi-layer architectural validation
Best use case
boundary-policy-classification-by-role is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Classify artifacts as durable vs transient by their functional role rather than directory path, using multi-layer architectural validation
Teams using boundary-policy-classification-by-role should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/boundary-policy-classification-by-role/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How boundary-policy-classification-by-role Compares
| Feature / Agent | boundary-policy-classification-by-role | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Classify artifacts as durable vs transient by their functional role rather than directory path, using multi-layer architectural validation
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Boundary Policy Classification by Role
When defining durable vs transient artifact boundaries within a multi-layer architecture, classify by *role* not *path*. Same directory can contain both types (e.g., reports/ has one-shot audits and durable assessments). Ground classification in concrete examples from each layer, validate consistency with parent architecture, and use adversarial review to test for loose language ('it depends') and implementability gaps.Related Skills
mixed-ops-vs-repo-fix-plan-boundary
Plan mixed operational-vs-repo remediation issues by proving live-state classification first, then only proposing code changes for confirmed repo-owned failure paths.
multi-role-agent-contract-review-pipeline
Execute a 4-role agent team (Planner/Architect/Reviewer/Integrator) pipeline for self-reviewing knowledge artifacts before delivery
provider-audit-bootstrap-and-path-classification
Fix provider-session ecosystem audit failures caused by source-checkout imports and over-aggressive symbolic-path classification.
post-smoke-ci-plan-boundary-hardening
Harden a CI follow-up plan after an initial smoke/unblock issue lands. Use for post-smoke red workflows where later gates surface broad lint/type debt and the plan must stay bounded, evidence-backed, and review-honest.
plan-governance-vs-execution-boundary-for-adversarial-review
Keep stale-approval/governance remediation out of execution-path pseudocode, TDD, files-to-change, and deliverable acceptance when hardening a GitHub issue plan under adversarial review.
pdf-text-extractor-readability-classification
Sub-skill of pdf-text-extractor: Readability Classification.
cross-review-policy
Actionable review routing policy — which agent reviews which agent's work, default three-agent adversarial review
hydrodynamic-analysis-1-boundary-element-method-bem
Sub-skill of hydrodynamic-analysis: 1. Boundary Element Method (BEM) (+1).
doc-extraction-hybrid-classification-strategy-wrk-1188-learning
Sub-skill of doc-extraction: Hybrid Classification Strategy (WRK-1188 Learning).
internal-comms-3-policy-memos
Sub-skill of internal-comms: 3. Policy Memos (+2).
agent-usage-optimizer-keyword-route-classification
Sub-skill of agent-usage-optimizer: Keyword → Route classification.
test-oversized-skill
A test fixture skill that exceeds 200 lines with multiple H2/H3 sections for split testing.