toss-phase13-gate

Analyze AUTH/IAP/MSG/AD end-to-end criteria and collect evidence for gate readiness.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/kimjuyoung1127/TaillogToss --skill toss-phase13-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: toss-phase13-gate
Source: https://github.com/kimjuyoung1127/TaillogToss/tree/main/.claude/skills/toss-phase13-gate
Command: npx skills add https://github.com/kimjuyoung1127/TaillogToss --skill toss-phase13-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase 13 gate readiness often requires consolidating test results, logs, and documentation across multiple teams. This skill provides a structured, evidence-driven approach to quickly assess AUTH/IAP/MSG/AD end-to-end criteria and align documentation status.

Core Features & Use Cases

  • Evidence-driven gate checks: automatically verify key criteria and collect logs and test results to support release decisions.
  • Cross-functional readiness: aggregates findings from engineering, product, and QA to inform priority setting and risk assessment.
  • Documentation synchronization: updates gate status and remaining actions in a single, auditable record to keep all stakeholders aligned.

Quick Start

Run the phase13 gate check for the current release to generate evidence-based pass/fail status and synchronize documents.

Frequently Asked Questions about toss-phase13-gate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify Phase 13 gate readiness with evidence for AUTH and IAP releases?

Phase 13 gate readiness is verified by analyzing AUTH/IAP/MSG/AD end-to-end criteria and collecting logs, tests, and deployment evidence to generate an evidence-backed pass/fail status.

What is the best way to consolidate release readiness checks across engineering, product, and QA teams?

Release readiness is consolidated by aggregating cross-functional findings from engineering, product, and QA into a single auditable record that synchronizes documentation and informs risk assessment.

How do I synchronize gate status and remaining actions for a Phase 13 rolling migration?

Gate status synchronization updates the referenced PHASE13-FE-BE-ROLLING-MIGRATION documentation and MISSING-AND-UNIMPLEMENTED records to align all stakeholders with remaining release actions.

Do I need specific documentation inputs to assess feature parity for release gate checks?

Feature parity assessment requires inputs from CLAUDE.md, FEATURE-PARITY-MATRIX, and MISSING-AND-UNIMPLEMENTED docs to validate logs, tests, and deployment status for the gate check.

Can I automate evidence collection for end-to-end AUTH and MSG release criteria?

Evidence collection runs automatically during the phase13 gate check to verify key criteria, collect test results, and support release decisions without manual log aggregation.

Why does my Phase 13 documentation fall out of sync after cross-functional gate readiness assessments?

Documentation falls out of sync when gate readiness findings are not consolidated into a single auditable record; the skill updates gate status and remaining actions to keep stakeholders aligned.