← all publishers

yknothing

@yknothing source repo

Report this profile Claim this profile

• 119 skills
• 0 followers
• 4 hours ago last updated

1. ▌
   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.
   0
   installs
2. ▌
   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.
   0
   installs
3. ▌
   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.
   0
   installs
4. ▌
   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.
   0
   installs
5. ▌
   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.
   0
   installs
6. ▌
   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.
   0
   installs
7. ▌
   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
   0
   installs
8. ▌
   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.
   0
   installs
9. ▌
   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.
   0
   installs
10. ▌
    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.
    0
    installs
11. ▌
    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.
    0
    installs
12. ▌
    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.
    0
    installs
13. ▌
    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).
    0
    installs
14. ▌
    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.
    0
    installs
15. ▌
    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.
    0
    installs
16. ▌
    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".
    0
    installs
17. ▌
    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.
    0
    installs
18. ▌
    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.
    0
    installs
19. ▌
    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.
    0
    installs
20. ▌
    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.
    0
    installs
21. ▌
    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.
    0
    installs
22. ▌
    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.
    0
    installs
23. ▌
    Pc Acceptance Criteria 2 · yknothing bundle

    Use when defining testable criteria that determine whether a requirement is met
    0
    installs
24. ▌
    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.
    0
    installs
25. ▌
    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.
    0
    installs
26. ▌
    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.
    0
    installs
27. ▌
    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.
    0
    installs
28. ▌
    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.
    0
    installs
29. ▌
    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.
    0
    installs
30. ▌
    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.
    0
    installs
31. ▌
    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.
    0
    installs
32. ▌
    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.
    0
    installs
33. ▌
    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.
    0
    installs
34. ▌
    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.
    0
    installs
35. ▌
    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.
    0
    installs
36. ▌
    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.
    0
    installs
37. ▌
    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
    0
    installs
38. ▌
    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.
    0
    installs
39. ▌
    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.
    0
    installs
40. ▌
    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.
    0
    installs
41. ▌
    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.
    0
    installs
42. ▌
    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.
    0
    installs
43. ▌
    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.
    0
    installs
44. ▌
    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”.
    0
    installs
45. ▌
    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.
    0
    installs
46. ▌
    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.
    0
    installs
47. ▌
    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.
    0
    installs
48. ▌
    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.
    0
    installs
49. ▌
    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.
    0
    installs
50. ▌
    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.
    0
    installs
51. ▌
    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.
    0
    installs
52. ▌
    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.
    0
    installs
53. ▌
    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.
    0
    installs
54. ▌
    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.
    0
    installs
55. ▌
    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.
    0
    installs
56. ▌
    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.
    0
    installs
57. ▌
    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.
    0
    installs
58. ▌
    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.
    0
    installs
59. ▌
    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.
    0
    installs
60. ▌
    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.
    0
    installs
61. ▌
    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.
    0
    installs
62. ▌
    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.
    0
    installs
63. ▌
    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.
    0
    installs
64. ▌
    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.
    0
    installs
65. ▌
    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.
    0
    installs
66. ▌
    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.
    0
    installs
67. ▌
    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.
    0
    installs
68. ▌
    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.
    0
    installs
69. ▌
    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.
    0
    installs
70. ▌
    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.
    0
    installs
71. ▌
    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.
    0
    installs
72. ▌
    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.
    0
    installs
73. ▌
    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.
    0
    installs
74. ▌
    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.
    0
    installs
75. ▌
    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
    0
    installs
76. ▌
    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.
    0
    installs
77. ▌
    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.
    0
    installs
78. ▌
    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.
    0
    installs
79. ▌
    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.
    0
    installs
80. ▌
    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.
    0
    installs
81. ▌
    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
    0
    installs
82. ▌
    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.
    0
    installs
83. ▌
    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.
    0
    installs
84. ▌
    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.
    0
    installs
85. ▌
    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.
    0
    installs
86. ▌
    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.
    0
    installs
87. ▌
    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.
    0
    installs
88. ▌
    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.
    0
    installs
89. ▌
    Pc Acceptance Criteria · yknothing bundle

    Use when defining testable criteria that determine whether a requirement is met
    0
    installs
90. ▌
    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".
    0
    installs
91. ▌
    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.
    0
    installs
92. ▌
    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).
    0
    installs
93. ▌
    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.
    0
    installs
94. ▌
    Pc Market Analysis · yknothing bundle

    Use when discovery needs evidence about market demand, competitors, pricing pressure, or underserved segments for a new product or expansion idea before feasibility, user research, or requirements are finalized.
    0
    installs
95. ▌
    Pc Systematic Debugging · 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.
    0
    installs
96. ▌
    Pc Tech Debt Management · 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.
    0
    installs
97. ▌
    Pc Receiving Code Review · 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.
    0
    installs
98. ▌
    Pc Feasibility Study · yknothing bundle

    Use when discovery has narrowed an idea enough that the team must make a go/no-go, pivot, or scope-down decision based on technical, economic, operational, or timeline viability before requirements, architecture, or major implementation.
    0
    installs
99. ▌
    Pc Monitoring Observability · 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.
    0
    installs
100. ▌
     Pc Requirements Engineering · 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.
     0
     installs