Skip to content

[Improvement] Add authentication recovery workflow pack - #82

Open
RanveerSinghRajput024 wants to merge 1 commit into
FinanceFlash:mainfrom
RanveerSinghRajput024:feature/authentication-recovery-workflow
Open

[Improvement] Add authentication recovery workflow pack#82
RanveerSinghRajput024 wants to merge 1 commit into
FinanceFlash:mainfrom
RanveerSinghRajput024:feature/authentication-recovery-workflow

Conversation

@RanveerSinghRajput024

Copy link
Copy Markdown

Problem and scope

Add a focused pre-built workflow pack covering authentication, login, session management, and account recovery. The scope covers common authentication and recovery paths, edge cases, permissions and abuse considerations, retry/recovery, testing, and business context.

Describe the user problem and the focused scope of this change.

What changed

Added the authentication-login-session-and-account-recovery workflow pack with 13 required documentation and skill files covering scenarios, engineering guidance, edge cases, permissions, business context, retry/recovery, testing, and workflow implementation.

Summarize the implementation or content change.

Verification

List the commands, fixtures, public repositories, and outputs used to verify the change.

  • 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
  • I used UnvibeCode on a representative repository when the change affects code analysis, CLI behaviour, engineering guidance, or code-specific claims.
    ☑ I updated documentation for changed user-facing behaviour.
    ☑ 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 names.

Remaining limitations

No known limitations. The contribution is focused on adding the authentication, login, session management, and account recovery workflow pack.

List any known limitation or follow-up issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant