all publishers

yknothing

@yknothing source repo

126 published skills · page 1 of 2

  1. ▌
    Pc Debug Expert · yknothing bundle
    Use when bugs, failing tests, regressions, flaky behavior, performance degradation, or runtime and skill-loading failures need causal diagnosis, especially when symptoms are ambiguous or attempted fixes have failed.
    1 repo stars
  2. ▌
    Pc Debug Expert 2 · yknothing bundle
    Use when bugs, failing tests, regressions, flaky behavior, performance degradation, or runtime and skill-loading failures need causal diagnosis, especially when symptoms are ambiguous or attempted fixes have failed.
    1 repo stars
  3. ▌
    Pc E2e Scenario Design 3 · yknothing bundle
    Use when E2E tests must go beyond shallow happy-path checks — multi-step user journeys, stateful sessions, cross-boundary state consistency, failure-mode edges — or when the suite passes but production still breaks. Platform- and framework-agnostic (web, mobile, desktop; Playwright, XCUITest, Cypress).
    1 repo stars
  4. ▌
    Pc Systematic Debugging 3 · yknothing bundle
    Use when a bug, failing test, regression, or unexpected behavior needs a root-cause-first debugging loop before code changes, especially when brownfield seams, recent releases, or historical defect matches make guesswork unsafe.
    1 repo stars
  5. ▌
    Problem Framing 2 · yknothing
    Use when intake has identified the likely lifecycle path but the problem statement, solution direction, or key trade-offs are still too fuzzy for requirements, research, or architecture work to start cleanly
    1 repo stars
  6. ▌
    User Research 2 · yknothing
    Use when discovery needs evidence about target users, behaviors, and pain points, especially after intake or problem-framing surfaces open questions that must be validated before requirements are written
    1 repo stars
  7. ▌
    Requirements Engineering 3 · yknothing
    Use when the work is still at the “what should we build” stage rather than design or implementation. Apply before spec-writing, architecture, API design, planning, or coding when interviews, personas, stakeholder notes, or discovery artifacts must be turned into prioritized functional requirements, non-functional requirements, scope boundaries, traceable sources, and explicit “the system shall” statements; not for acceptance criteria, PRD drafting from an approved requirements doc, spec review, or implementation.
    1 repo stars
  8. ▌
    Pc Risk Assessment 2 · yknothing bundle
    Use when planned work must be challenged for delivery, dependency, migration, security, or operational risk before the team commits to scope or sequence.
    1 repo stars
  9. ▌
    Pc Sprint Planning 2 · yknothing bundle
    Use when the team has sized work and must choose a realistic iteration scope, sequence, and ownership model that fits capacity and current risk.
    1 repo stars
  10. ▌
    Pc Testing Strategy 2 · yknothing bundle
    Use when a reviewed implementation slice or feature needs a deliberate test plan across unit, integration, contract, and end-to-end layers, especially when brownfield regressions, unsupported flows, coexistence boundaries, or API contracts require explicit coverage beyond the default happy path.
    1 repo stars
  11. ▌
    Pc Accessibility 2 · yknothing bundle
    Use when a user interface, user-facing flow, or acceptance criteria need accessibility requirements, audits, or remediation guidance so the system stays usable for people with disabilities.
    1 repo stars
  12. ▌
    Pc Documentation 2 · yknothing bundle
    Use when a feature, architecture decision, incident, or workflow change needs durable technical documentation such as tutorials, reference docs, ADRs, runbooks, or maintenance guidance instead of ad hoc notes.
    1 repo stars
  13. ▌
    Pc Observability 2 · yknothing bundle
    Use when code, workflows, or AI execution paths need structured telemetry such as logs, metrics, traces, skill-invocation records, model-usage accounting, or token usage records so behavior, failures, and cost stay observable across the lifecycle.
    1 repo stars
  14. ▌
    Pc Problem Framing 2 · yknothing bundle
    Use when intake has identified the likely lifecycle path but the problem statement, solution direction, or key trade-offs are still too fuzzy for requirements, research, or architecture work to start cleanly
    1 repo stars
  15. ▌
    Pc Spec Writing 2 · yknothing bundle
    Use when reviewed requirements need a shared product or technical specification that fixes scope, non-goals, interfaces, rollout concerns, and open questions before architecture or implementation. Skip for routine agile story refinement.
    1 repo stars
  16. ▌
    Pc Data Modeling 2 · yknothing bundle
    Use when the system structure is known and the team must turn domain concepts and architectural boundaries into durable storage schemas, ownership rules, and migration-safe data flow decisions before implementation.
    1 repo stars
  17. ▌
    Pc System Design 2 · yknothing bundle
    Use when reviewed requirements or specifications are ready and the team must decide high-level architecture, component boundaries, integration seams, or brownfield coexistence strategy before API design, technology selection, or task planning.
    1 repo stars
  18. ▌
    Pc Refactoring 2 · yknothing bundle
    Use when existing code is correct but structurally costly to change, and the team needs to improve clarity, coupling, duplication, or seam quality without changing externally observable behavior.
    1 repo stars
  19. ▌
    Pc Tech Selection 2 · yknothing bundle
    Use when the architecture is known and the team must choose concrete languages, frameworks, data stores, or infrastructure tools with explicit trade-offs instead of letting implementation drift into ad hoc stack decisions.
    1 repo stars
  20. ▌
    Pc E2e Scenario Design 2 · yknothing bundle
    Use when E2E tests must go beyond shallow happy-path checks — multi-step user journeys, stateful sessions, cross-boundary state consistency, failure-mode edges — or when the suite passes but production still breaks. Platform- and framework-agnostic (web, mobile, desktop; Playwright, XCUITest, Cypress).
    1 repo stars
  21. ▌
    Pc Release Management 2 · yknothing bundle
    Use when a tested release candidate needs a coordinated go/no-go decision, release window, communication path, and ownership model before deployment proceeds.
    1 repo stars
  22. ▌
    Pc Security Design 2 · yknothing bundle
    Use when the architecture is defined and the team must turn trust boundaries, sensitive data paths, and attacker assumptions into concrete control design before implementation and audit.
    1 repo stars
  23. ▌
    Pc Delivery Completion 2 · yknothing bundle
    Use when verified implementation work must be merged, handed off through a PR, preserved for later, or explicitly discarded with a recorded outcome instead of an ambiguous "done".
    1 repo stars
  24. ▌
    Pc Deployment Strategy 2 · yknothing bundle
    Use when a release candidate is ready and the team must choose the safest rollout pattern, verification checkpoints, and rollback path for the current risk, blast radius, and operational constraints.
    1 repo stars
  25. ▌
    Pc Incident Response 2 · yknothing bundle
    Use when a live production issue needs coordinated containment, severity triage, stakeholder communication, and evidence capture, especially when a recent release, brownfield coexistence rules, rollback decisions, or unresolved contract boundaries must be handled before root-cause work.
    1 repo stars
  26. ▌
    Pc Domain Modeling 2 · yknothing bundle
    Use when reviewed requirements still carry ambiguous business nouns, overlapping concepts, or possible bounded contexts, and the team needs a shared domain model before spec writing, API design, or data modeling.
    1 repo stars
  27. ▌
    Pc Task Execution 2 · yknothing bundle
    Use when an approved task slice already exists and the team needs a 2-5 minute execution plan with checkpoints, stop conditions, and batch discipline before or during implementation, especially when brownfield seams or review-sensitive changes make ad hoc execution unsafe.
    1 repo stars
  28. ▌
    Pc Receiving Code Review 2 · yknothing bundle
    Use when review feedback has arrived and the author must verify, sequence, and respond to comments without blind agreement, especially when suggestions may conflict with brownfield constraints, contracts, or existing architecture decisions.
    1 repo stars
  29. ▌
    Pc Tech Debt Management 2 · yknothing bundle
    Use when repeated findings from reviews, incidents, retrospectives, or delivery friction need to be turned into a prioritized technical-debt registry and remediation plan, especially when brownfield seams, release-boundary gaps, or operational workarounds are accruing real engineering cost.
    1 repo stars
  30. ▌
    Pc Acceptance Criteria 2 · yknothing bundle
    Use when defining testable criteria that determine whether a requirement is met
    1 repo stars
  31. ▌
    Pc Feature Development 2 · yknothing bundle
    Use when a reviewed task slice has tests or acceptance targets and the team must turn it into a small, mergeable implementation increment without expanding scope, breaking contracts, or hiding release-boundary risk.
    1 repo stars
  32. ▌
    Pc Systematic Debugging 2 · yknothing bundle
    Use when a bug, failing test, regression, or unexpected behavior needs a root-cause-first debugging loop before code changes, especially when brownfield seams, recent releases, or historical defect matches make guesswork unsafe.
    1 repo stars
  33. ▌
    Pc Monitoring Observability 2 · yknothing bundle
    Use when a live service or newly delivered release needs actionable telemetry, dashboards, and alerts that expose real user-impactful boundaries, especially when brownfield coexistence rules, unsupported-flow safety, rollback health, or queue/backfill behavior must be visible before incidents escalate.
    1 repo stars
  34. ▌
    Pc Requirements Engineering 2 · yknothing bundle
    Use when the work is still at the “what should we build” stage and approved discovery inputs or entry-stack outputs must become prioritized requirements and scope boundaries before specification, architecture, planning, or coding. Not for acceptance criteria, spec review, or implementation.
    1 repo stars
  35. ▌
    Pc Verification Before Completion 2 · yknothing bundle
    Use when about to claim a phase, fix, task, build, or release is complete, fixed, passing, or ready for handoff and fresh evidence must be checked before making the claim or creating a commit, PR, or deployment decision.
    1 repo stars
  36. ▌
    Requirements Engineering 2 · yknothing
    Use when the work is still at the “what should we build” stage rather than design or implementation. Apply before spec-writing, architecture, API design, planning, or coding when interviews, personas, stakeholder notes, or discovery artifacts must be turned into prioritized functional requirements, non-functional requirements, scope boundaries, traceable sources, and explicit “the system shall” statements; not for acceptance criteria, PRD drafting from an approved requirements doc, spec review, or implementation.
    1 repo stars
  37. ▌
    Pc CI CD 2 · yknothing bundle
    Use when a reviewed implementation slice needs an automated build, test, and deployment pipeline, especially when brownfield rollback, release-boundary checks, contract/integration gates, and staged delivery must be explicit before shipping.
    1 repo stars
  38. ▌
    Pc Intake 2 · yknothing bundle
    The mandatory gateway for all new engineering work. Triage and route new products, apps, features, migrations, tech-debt, or any 'not sure where to start' request to the correct lifecycle path. Use before starting design or implementation. Do not use for ongoing tasks, specific debugging, or PR reviews.
    1 repo stars
  39. ▌
    Pc Tdd 2 · yknothing bundle
    Use when a reviewed task is ready for implementation and the team must drive the work by writing failing tests first, especially when contract behavior, brownfield regressions, unsupported flows, or coexistence safety must be proven before code changes.
    1 repo stars
  40. ▌
    Pc Estimation 2 · yknothing bundle
    Use when reviewed tasks exist and the team must size them with explicit assumptions, confidence, and risk awareness before committing to a timeline or sprint scope.
    1 repo stars
  41. ▌
    Pc Code Review 2 · yknothing bundle
    Use when a concrete code change is ready for review and the reviewer must evaluate correctness, security, maintainability, test adequacy, contract alignment, and brownfield safety before merge, especially when unsupported flows, backward compatibility, or release-boundary constraints must be enforced.
    1 repo stars
  42. ▌
    Pc Runbooks 2 · yknothing bundle
    Use when an operational task or incident needs a concrete step-by-step procedure that another responder can execute safely, especially when rollback, fail-closed containment, coexistence fallback, communication cadence, or evidence capture must be explicit under pressure.
    1 repo stars
  43. ▌
    Pc Security Audit 2 · yknothing bundle
    Use when a reviewed change, release candidate, or high-risk slice must be challenged for abuse paths, trust-boundary failures, secret handling, dependency risk, or data exposure before release.
    1 repo stars
  44. ▌
    Pc User Research 2 · yknothing bundle
    Use when discovery needs evidence about target users, behaviors, and pain points, especially after intake or problem-framing surfaces open questions that must be validated before requirements are written
    1 repo stars
  45. ▌
    Pc API Design 2 · yknothing bundle
    Use when architecture boundaries are already defined and the team must specify stable API contracts between components or for external consumers, especially when backward compatibility, brownfield coexistence, authorization rules, and error semantics must be made explicit before implementation.
    1 repo stars
  46. ▌
    Pc Task Breakdown 2 · yknothing bundle
    Use when reviewed architecture or API contracts must be decomposed into implementation-ready work items, especially when sequencing, reversible brownfield increments, dependency mapping, and vertical slices must be explicit before coding begins.
    1 repo stars
  47. ▌
    Pc Retrospective 2 · yknothing bundle
    Use when a sprint, release, or incident has ended and the team needs to turn evidence about what worked, what failed, and what should change into a small set of owned follow-up actions.
    1 repo stars
  48. ▌
    Skill Debug · yknothing bundle
    Use when you need local evidence about whether agent skills are on likely discovery surfaces, whether activation canaries were observed, and which installed skill identities have no local canary evidence.
    1 repo stars
  49. ▌
    Skill Hygiene · yknothing bundle
    Use when you need to audit, evaluate, govern, safely retire, or transactionally upgrade locally installed or distributed agent skills. Triggers include skill sprawl, stale, broken, or conflicting skills, local cleanup or quarantine, managed physical collections, pre-migration review, and periodic inventory checks.
    1 repo stars
  50. ▌
    Skills Refiner · yknothing bundle
    Audit and refine a skill repository, a single skill, a workflow framework, or an eval set. Covers design quality, context engineering, purpose fit, evidence discipline, and boundary clarity — the structural dimensions that assertion-based testing does not reach. When a target_repo is provided, continues into compatibility review, extraction, and integration planning. Complements skill-creator by providing deep design-level judgment after functional tests pass.
    1 repo stars
  51. ▌
    Skills Panorama · yknothing bundle
    Use when the user wants a readable map of locally installed Agent Skills — what exists in the source store, which Agents see them, whether links and control-catalog intent match reality, and how to triage gaps without mutating anything. Triggers include 技能全景, installed skills overview, topology map, projection drift, and “what is on this machine”.
    1 repo stars
  52. ▌
    Skills Appreciation · yknothing bundle
    Explain and interpret a skill, a skills repository, or a skills system in a deep yet accessible teaching style. Use when the goal is to help readers truly understand how it works, why it works, what is worth learning, and how to design better skills.
    1 repo stars
  53. ▌
    Bs Prdefine · yknothing
    Use when the user needs to define Product Requirements (PR) for a feature, product, or project from ambiguity through a reviewable handoff — especially when the ask is multi-stakeholder or high-stakes. Also use when requirement gaps are being filled with assumptions or someone pushes to skip clarification and just write a spec. This defines requirements; it is not merely a PRD template or document-writing workflow.
    1 repo stars
  54. ▌
    Bs Sw Master · yknothing bundle
    Use when the user wants to master and complete a Software (SW) change from a spec, requirements document, or issue — including acceptance criteria, isolated setup, safe snapshots, characterization or TDD, implementation, self-review, a reviewable commit, and authorized push. This does not imply deployment, production operations, or unrelated opportunistic changes.
    1 repo stars
  55. ▌
    Bs UI Master · yknothing bundle
    Use when the user asks to design or substantially improve a product UI, page, screen, component, or visual system. Covers visual direction, tokens, layout, color, typography, spacing, imagery, interaction states, motion, accessibility, and visual QA. This is production-grade UI design, not a complete UX practice: it does not claim user research, information architecture, journey mapping, or usability studies.
    1 repo stars
  56. ▌
    Bs Ppt Master · yknothing bundle
    Use when creating, revising, filling, or enhancing a PPT or slide deck whose argument, visual system, editability, details, and final artifact must be designed and verified together.
    1 repo stars
  57. ▌
    Bs Uml Master · yknothing bundle
    Use when creating, revising, or reviewing UML or architecture diagrams — class, sequence, state machine, activity, component, deployment, use case, ER, or C4 — from a codebase or a design, where diagram-type fit, semantic correctness, abstraction discipline, and render-verified delivery matter.
    1 repo stars
  58. ▌
    Bs Skill Forge · yknothing bundle
    Use when the user wants to forge a new Agent Skill from idea to publishable delivery, including Reference-vs-Build judgment, capability definition, pattern selection, TDD, four review gates, and registry integration. Use this for new Skill creation, not for silently rewriting an existing Skill or bypassing independent audit.
    1 repo stars
  59. ▌
    Bs Social Card · yknothing bundle
    Use when the user asks to produce and validate a single 1200x630 social media card, Open Graph image, Twitter card, link preview, or social share graphic. Do not use for full-page screenshots, multi-slide carousels, animated GIFs, video thumbnails, print-ready graphics, or a general-purpose visual identity system.
    1 repo stars
  60. ▌
    Bs Prose Master · yknothing
    Use when the user asks to master, improve, rewrite, polish, or craft prose — including structure, rhythm, precision, audience fit, tone, or article flow. Also use when edits risk drifting toward generic corporate language, flattening the author's voice, or adding unsupported claims. Bilingual Chinese and English editing is supported; translation alone is not the trigger.
    1 repo stars
  61. ▌
    Bs Reflect Loop · yknothing bundle
    Use when retrospectives and future-practice learning are requested after completed or stable work, including requests to extract lessons, tighten rules, prevent recurrence, or deposit evidence-bounded learning. Re-evaluate routing when a conversation moves from active diagnosis to reflection. Do not use while diagnosis, incident response, or implementation is still active, for summary-only requests, or as permission to modify executable or governance surfaces.
    1 repo stars
  62. ▌
    Bs Skill Auditor · yknothing
    Use when you need a read-only, evidence-anchored audit of installed agent skills across structure, safety, freshness, and pattern alignment, including confidence scoring, failure routing, and a health report. This skill diagnoses and recommends; it does not directly repair the audited skills or execute them dynamically.
    1 repo stars
  63. ▌
    Bs Visual Article · yknothing bundle
    Use when the user wants to turn an article, blog post, or long-form document into a coherent visual article by planning, generating, placing, and validating diagrams, charts, conceptual illustrations, or comparison visuals. Use visuals only when they improve understanding; do not use this for decorative image insertion, a single poster, or invented data.
    1 repo stars
  64. ▌
    Bs Insight Product · yknothing bundle
    Use when a software product or SaaS idea needs evidence, dissent, and adversarial pressure turned into a product-direction decision — including discovery, positioning, wedge selection, repositioning, or a pursue, test, park, or kill judgment before requirements or implementation begin. This does not certify product-market fit.
    1 repo stars
  65. ▌
    Bs Prospect Customer · yknothing bundle
    Use when the user wants to prospect, qualify, and prioritize first customers, early adopters, design partners, or beta users from recent public evidence, then design a human validation experiment. This is evidence-backed first-customer prospecting, not lead scraping, private-contact enrichment, automated outreach, or a promise of conversion.
    1 repo stars
  66. ▌
    Pc Tdd · yknothing bundle
    Use when a reviewed task is ready for implementation and the team must drive the work by writing failing tests first, especially when contract behavior, brownfield regressions, unsupported flows, or coexistence safety must be proven before code changes.
    1 repo stars
  67. ▌
    Pc CI CD · yknothing bundle
    Use when a reviewed implementation slice needs an automated build, test, and deployment pipeline, especially when brownfield rollback, release-boundary checks, contract/integration gates, and staged delivery must be explicit before shipping.
    1 repo stars
  68. ▌
    Pc Intake · yknothing bundle
    The mandatory gateway for all new engineering work. Triage and route new products, apps, features, migrations, tech-debt, or any 'not sure where to start' request to the correct lifecycle path. Use before starting design or implementation. Do not use for ongoing tasks, specific debugging, or PR reviews.
    1 repo stars
  69. ▌
    Pc Runbooks · yknothing bundle
    Use when an operational task or incident needs a concrete step-by-step procedure that another responder can execute safely, especially when rollback, fail-closed containment, coexistence fallback, communication cadence, or evidence capture must be explicit under pressure.
    1 repo stars
  70. ▌
    Pc Prodcraft · yknothing bundle
    Use when software-development work is underway or likely, so the task routes through the Prodcraft lifecycle-aware entry stack before planning, implementation, quality gates, or workflow selection. Default to Prodcraft for software-development unless the user explicitly chooses another path.
    1 repo stars
  71. ▌
    Pc API Design · yknothing bundle
    Use when architecture boundaries are already defined and the team must specify stable API contracts between components or for external consumers, especially when backward compatibility, brownfield coexistence, authorization rules, and error semantics must be made explicit before implementation.
    1 repo stars
  72. ▌
    Pc Estimation · yknothing bundle
    Use when reviewed tasks exist and the team must size them with explicit assumptions, confidence, and risk awareness before committing to a timeline or sprint scope.
    1 repo stars
  73. ▌
    Pc Code Review · yknothing bundle
    Use when a concrete code change is ready for review and the reviewer must evaluate correctness, security, maintainability, test adequacy, contract alignment, and brownfield safety before merge, especially when unsupported flows, backward compatibility, or release-boundary constraints must be enforced.
    1 repo stars
  74. ▌
    Pc Refactoring · yknothing bundle
    Use when existing code is correct but structurally costly to change, and the team needs to improve clarity, coupling, duplication, or seam quality without changing externally observable behavior.
    1 repo stars
  75. ▌
    Pc Spec Writing · yknothing bundle
    Use when reviewed requirements need a shared product or technical specification that fixes scope, non-goals, interfaces, rollout concerns, and open questions before architecture or implementation. Skip for routine agile story refinement.
    1 repo stars
  76. ▌
    Pc Accessibility · yknothing bundle
    Use when a user interface, user-facing flow, or acceptance criteria need accessibility requirements, audits, or remediation guidance so the system stays usable for people with disabilities.
    1 repo stars
  77. ▌
    Pc Data Modeling · yknothing bundle
    Use when the system structure is known and the team must turn domain concepts and architectural boundaries into durable storage schemas, ownership rules, and migration-safe data flow decisions before implementation.
    1 repo stars
  78. ▌
    Pc Documentation · yknothing bundle
    Use when a feature, architecture decision, incident, or workflow change needs durable technical documentation such as tutorials, reference docs, ADRs, runbooks, or maintenance guidance instead of ad hoc notes.
    1 repo stars
  79. ▌
    Pc Observability · yknothing bundle
    Use when code, workflows, or AI execution paths need structured telemetry such as logs, metrics, traces, skill-invocation records, model-usage accounting, or token usage records so behavior, failures, and cost stay observable across the lifecycle.
    1 repo stars
  80. ▌
    Pc Retrospective · yknothing bundle
    Use when a sprint, release, or incident has ended and the team needs to turn evidence about what worked, what failed, and what should change into a small set of owned follow-up actions.
    1 repo stars
  81. ▌
    Pc System Design · yknothing bundle
    Use when reviewed requirements or specifications are ready and the team must decide high-level architecture, component boundaries, integration seams, or brownfield coexistence strategy before API design, technology selection, or task planning.
    1 repo stars
  82. ▌
    Pc User Research · yknothing bundle
    Use when discovery needs evidence about target users, behaviors, and pain points, especially after intake or problem-framing surfaces open questions that must be validated before requirements are written
    1 repo stars
  83. ▌
    Pc Security Audit · yknothing bundle
    Use when a reviewed change, release candidate, or high-risk slice must be challenged for abuse paths, trust-boundary failures, secret handling, dependency risk, or data exposure before release.
    1 repo stars
  84. ▌
    Pc Task Breakdown · yknothing bundle
    Use when reviewed architecture or API contracts must be decomposed into implementation-ready work items, especially when sequencing, reversible brownfield increments, dependency mapping, and vertical slices must be explicit before coding begins.
    1 repo stars
  85. ▌
    Pc Task Execution · yknothing bundle
    Use when an approved task slice already exists and the team needs a 2-5 minute execution plan with checkpoints, stop conditions, and batch discipline before or during implementation, especially when brownfield seams or review-sensitive changes make ad hoc execution unsafe.
    1 repo stars
  86. ▌
    Pc Tech Selection · yknothing bundle
    Use when the architecture is known and the team must choose concrete languages, frameworks, data stores, or infrastructure tools with explicit trade-offs instead of letting implementation drift into ad hoc stack decisions.
    1 repo stars
  87. ▌
    Pc Domain Modeling · yknothing bundle
    Use when reviewed requirements still carry ambiguous business nouns, overlapping concepts, or possible bounded contexts, and the team needs a shared domain model before spec writing, API design, or data modeling.
    1 repo stars
  88. ▌
    Pc Problem Framing · yknothing bundle
    Use when intake has identified the likely lifecycle path but the problem statement, solution direction, or key trade-offs are still too fuzzy for requirements, research, or architecture work to start cleanly
    1 repo stars
  89. ▌
    Pc Risk Assessment · yknothing bundle
    Use when planned work must be challenged for delivery, dependency, migration, security, or operational risk before the team commits to scope or sequence.
    1 repo stars
  90. ▌
    Pc Security Design · yknothing bundle
    Use when the architecture is defined and the team must turn trust boundaries, sensitive data paths, and attacker assumptions into concrete control design before implementation and audit.
    1 repo stars
  91. ▌
    Pc Sprint Planning · yknothing bundle
    Use when the team has sized work and must choose a realistic iteration scope, sequence, and ownership model that fits capacity and current risk.
    1 repo stars
  92. ▌
    Pc Compliance · yknothing bundle
    Use when legal, contractual, regulatory, or internal policy requirements must be translated into engineering constraints, evidence, and approval checkpoints before delivery.
    1 repo stars
  93. ▌
    Pc Testing Strategy · yknothing bundle
    Use when a reviewed implementation slice or feature needs a deliberate test plan across unit, integration, contract, and end-to-end layers, especially when brownfield regressions, unsupported flows, coexistence boundaries, or API contracts require explicit coverage beyond the default happy path.
    1 repo stars
  94. ▌
    Pc Incident Response · yknothing bundle
    Use when a live production issue needs coordinated containment, severity triage, stakeholder communication, and evidence capture, especially when a recent release, brownfield coexistence rules, rollback decisions, or unresolved contract boundaries must be handled before root-cause work.
    1 repo stars
  95. ▌
    Pc Release Management · yknothing bundle
    Use when a tested release candidate needs a coordinated go/no-go decision, release window, communication path, and ownership model before deployment proceeds.
    1 repo stars
  96. ▌
    Pc Acceptance Criteria · yknothing bundle
    Use when defining testable criteria that determine whether a requirement is met
    1 repo stars
  97. ▌
    Pc Delivery Completion · yknothing bundle
    Use when verified implementation work must be merged, handed off through a PR, preserved for later, or explicitly discarded with a recorded outcome instead of an ambiguous "done".
    1 repo stars
  98. ▌
    Pc Deployment Strategy · yknothing bundle
    Use when a release candidate is ready and the team must choose the safest rollout pattern, verification checkpoints, and rollback path for the current risk, blast radius, and operational constraints.
    1 repo stars
  99. ▌
    Pc E2e Scenario Design · yknothing bundle
    Use when E2E tests must go beyond shallow happy-path checks — multi-step user journeys, stateful sessions, cross-boundary state consistency, failure-mode edges — or when the suite passes but production still breaks. Platform- and framework-agnostic (web, mobile, desktop; Playwright, XCUITest, Cypress).
    1 repo stars
  100. ▌
    Pc Feature Development · yknothing bundle
    Use when a reviewed task slice has tests or acceptance targets and the team must turn it into a small, mergeable implementation increment without expanding scope, breaking contracts, or hiding release-boundary risk.
    1 repo stars