Problem and scope

Applications that create and manage API credentials need a clear workflow for authorization, scope, activation, expiry, rotation, revocation, and recovery. Without a dedicated workflow pack, these lifecycle paths and failure cases can be missed during code review.

This contribution adds a focused API Credential Lifecycle Management workflow pack.

What changed

Added a complete pre-built workflow pack covering:

• Credential creation and activation
• Authorization and permission scope
• Credential expiry and renewal
• Planned and emergency rotation
• Credential revocation
• Concurrent and duplicate lifecycle operations
• Dependency failures and partial completion
• Retry, reconciliation, and recovery
• Audit and sensitive-data protection
• 20 core workflow scenarios
• Five task-specific LLM skills

Also linked the new workflow pack from prebuilt-workflow-paths/README.md.

Verification

• python -m black --config .github/quality/pyproject.toml --check .github/quality/tests
• python -m flake8 --config .github/quality/.flake8 .github/quality/tests
• python -m pytest -c .github/quality/pyproject.toml .github/quality/tests
• The quality suite passed: 626 tests passed.
• git diff --cached --check passed with no whitespace errors.
• The workflow pack contains exactly 20 core scenarios.
• All 13 required workflow-pack files are present.
• The pack was reviewed for consistent terminology across the product, engineering, scenario, testing, permission, recovery, and skill files.
• I included no credentials, proprietary source, customer data, generated customer reports, or unsanitized logs.

Workflow-pack checks

Complete these items only when adding or changing a pre-built workflow pack.

• The start, end, included scope, and excluded scope are explicit.
• The pack owns one primary business outcome and does not duplicate an existing pack.
• The 20 core scenarios are distinct and collectively cover the declared boundary.
• Every core scenario states what must not happen.
• All 13 required files use consistent People and systems, Things created or changed, Stages, and outcome terminology.

Remaining limitations

The workflow pack is technology-neutral and describes expected engineering controls rather than claiming that a particular implementation provides them. Repository-specific evidence should be established when the pack is applied to an actual codebase.