Qase Project Profile

• project_id
• qase_project_code
• env_contract
• intake_policy
• naming_policy
• governance_policy
• label_policy
• approval_policy
• artifact_policy

Optional Interface Keys

• work_item_policy
• naming_policy.authoritative_case_id_rules

Recommended naming_policy.authoritative_case_id_rules shape:

{
  "reject_prefixes": ["TBD-", "TEMP-", "TEST-", "SAMPLE-"],
  "reject_exact": ["UNKNOWN", "N/A", "NONE"],
  "reject_contains": ["example", "sample", "demo"]
}

Recommended work_item_policy shape:

{
  "source_type": "work-item",
  "adapter": "consumer-defined",
  "ref_precedence": ["external-ref", "title"]
}

Contract Files

• contract/qase-project-profile.contract.json
• consumer-provided references/<project>.qase-profile.json

Rules

1. This skill is the only consumer-variation layer for shared Qase behavior.
2. Shared core ships the contract and examples, not real consumer profile implementations.
3. Reads must remain non-gated by default.
4. Mutations must remain plan-first and approval-only by default.
5. Protected delete policy must be expressible through contract fields rather than hidden branching.
6. Artifact policy must align with the shared artifact contract.
7. Shared core may define authoritative-looking case-id hygiene, but consumer profiles still own the exact accepted case-id format.

Workflow

1. Load the consumer-provided profile reference and shared contract schema.
2. Validate required keys and nested policy requirements.
3. Publish project policy inputs for Qase hub, test-case, test-plan, execution, and governance skills, including any tracker adapter declaration.
4. Validate compatibility against qase-core-v1.

Invocation Format (Preferred)

$qase-project-profile project:<project-id> action:<load|validate|describe>

Invocation Examples

$qase-project-profile project:<project-id> action:validate
$qase-project-profile project:<project-id> action:describe

Output

• Validated shared Qase project-policy contract.
• Consumer-specific Qase policy inputs for the shared skill family.
• Compatibility result against the active Qase core version.

Validation

• Validate against contract/qase-project-profile.contract.json.
• Validate example profiles under examples/.
• Confirm profile fields cover governance, approval, and artifact behavior documented by the shared skills.
• Confirm naming_policy.canonical_case_id_format is consumer-specific while naming_policy.authoritative_case_id_rules stays generic and reusable.

Completion Criteria

1. The required policy surface is explicit and machine-checkable.
2. The shared core remains generic when a consumer profile changes.
3. Example profiles demonstrate default and stricter governance configurations.