Results for “proposal”

Develop evidence-backed structural and architectural security hardening proposals from vulnerability disclosures, supplied findings, incident or assessment documents, source code, or a completed Codex Security scan. Use when a user asks for systemic improvements, alternatives beyond per-finding patches, before-and-after security architecture views, engineering tradeoff analysis, or an implementation-ready plan for a selected hardening option. Also use automatically after a Codex Security scan with reportable findings when the top-level scan workflow requests final-report hardening guidance.

The English summary is being prepared. Showing the original description.

Systematic root-cause isolation and minimal fix proposal for software bugs.

The English summary is being prepared. Showing the original description.

Assesses conglomerate break-up activism with segment valuation, separation feasibility, and tax-free qualification analysis. Use when evaluating SOTP activism, analyzing break-up proposals, or modeling separation value.

The English summary is being prepared. Showing the original description.

Structures credit committee packages with borrower analysis, risk assessment, structuring proposal, and recommendation documentation. Use when preparing credit committee materials, presenting loan opportunities, or documenting credit decisions.

The English summary is being prepared. Showing the original description.

Evaluates management buyouts and take-private proposals with fairness assessment, minority squeeze-out mechanics, and appraisal rights analysis. Use when analyzing going-private deals, evaluating MBO fairness, or assessing minority shareholder protections.

The English summary is being prepared. Showing the original description.

Redact reverse-engineering findings for public disclosure while preserving methodology, generalizable patterns, and teaching value. Covers the private-vs-public repo split, deny-list pattern maintenance, orphan-commit publish pattern that prevents `git log` leaks, category-based redaction calibration (methodology/pattern/version-finding/internal), and the `check-redaction.sh`-style CI gate that blocks merges when a deny-listed pattern appears. Use when publishing findings about a CLI harness you don't own, when preparing upstream proposals to an unrelated project, or when archiving a private research repo for public reference.

The English summary is being prepared. Showing the original description.

Conduct a peer review of research methodology, experimental design, and manuscript quality. Covers methodology evaluation, statistical appropriateness, reproducibility assessment, bias identification, and constructive feedback. Use when reviewing a manuscript, preprint, or internal research report, evaluating a research proposal or study protocol, assessing evidence quality behind a claim, or reviewing a thesis chapter or dissertation section.

The English summary is being prepared. Showing the original description.

Systematically interpret nuclear magnetic resonance spectra (1H, 13C, DEPT, and 2D experiments) to elucidate molecular structure. Covers chemical shift assignment, coupling pattern analysis, integration, and correlation of multi-dimensional data into coherent structural proposals.

The English summary is being prepared. Showing the original description.

Generate a Quarto-based tour report with embedded maps, daily itineraries, logistics tables, and accommodation/transport details. Produces a self-contained HTML or PDF document suitable for offline use during travel. Use when compiling a planned tour into a shareable document, creating an offline-accessible travel guide, documenting a completed trip with photos and statistics, or producing a professional tour proposal for a group or client.

The English summary is being prepared. Showing the original description.

Evolve SKILL.md files from agent execution traces using a three-stage pipeline: trajectory collection from observed runs, parallel multi-agent patch proposal for error and success analysis, and conflict-free consolidation of overlapping edits via prevalence-weighting. Based on the Trace2Skill methodology.

The English summary is being prepared. Showing the original description.

Construct well-structured arguments using the hypothesis-argument-example triad. Covers formulating falsifiable hypotheses, building logical arguments (deductive, inductive, analogical, evidential), providing concrete examples, and steelmanning counterarguments. Use when writing or reviewing PR descriptions that propose technical changes, justifying design decisions in ADRs, constructing substantive code review feedback, or building a research argument or technical proposal.

The English summary is being prepared. Showing the original description.

Achieve distributed agreement without central authority using bee democracy, threshold voting, and quorum sensing. Covers proposal generation, advocacy dynamics, commitment thresholds, deadlock resolution, and consensus quality assessment. Use when a group must decide between options without a designated leader, when centralized decision-making is a bottleneck, when stakeholders have different perspectives to integrate, or when designing automated systems that must reach consensus such as distributed databases or multi-agent AI.

The English summary is being prepared. Showing the original description.

Use when stress-testing a proposal, plan, architecture or decision before committing to it, such as pre-mortems, assumption audits, "should we even do this?" questions, or when everyone agrees too easily. Not for code review; it challenges strategy, approach and hidden risks.

The English summary is being prepared. Showing the original description.

Create a new feature with proposal, retrospective, and branch. Use when starting new development work.

The English summary is being prepared. Showing the original description.

Use when any bounded workflow starts or reaches an action, path, proposal, or merge boundary. Refuses rather than default-allow on an unreadable constraint set.

The English summary is being prepared. Showing the original description.

Use when independent proposals on a contested decision need cross-critique before choosing, reusing the original authors. Not for parallel multi-stance investigation: use council.

The English summary is being prepared. Showing the original description.

Use when the user asks for a council, second opinions, or parallel investigation. Not for cross-examination of existing proposals: use cross-critique.

The English summary is being prepared. Showing the original description.

Use when an exact symbol, path, entrypoint, or line range can bound a focused code question or patch proposal under a fixed source budget. Not for source changes or broad repository exploration.

The English summary is being prepared. Showing the original description.

Select at most one eligible Proto UI work item and return a read-only proposal without changing GitHub or repository state. Use after pui-orient when requested contribution work is not yet bounded, or when a user asks what ready task fits the current capability and permission envelope. Do not post a claim, assign anyone, decide readiness, or invent work.

The English summary is being prepared. Showing the original description.

Post one already selected Proto UI work-item claim as a reversible GitHub metadata mutation. Use after pui-select produced a current proposal and the exact claim has authorization, live permission, current readiness, and an idempotent write boundary. Do not select work, decide readiness, release claims, or widen the authorized wording.

The English summary is being prepared. Showing the original description.

Use when a consumer repo needs proposal-first backlog, Registry, and Atlas drafts from new project intent before source exists.

The English summary is being prepared. Showing the original description.

Fires after fixing any non-trivial bug or regression. Asks: could the graph have caught this as a guarantee? Pairs with reflection-in-and-on-action — picks up after "earliest catchable signal" and asks the next question: was that signal expressible in graph? Triggers: (1) after any non-trivial bug fix is verified working, (2) after a regression report (something used to work, broke), (3) during step 6 (knowledge extraction) of the workflow, (4) when reflection-on-action surfaces a "would have been catchable" signal. Outcome is a triage decision (graph-reachable? rule expressible? rule sound?) and either a draft Linear issue + guarantee proposal, or a recorded "graph capability gap" note. Never auto-creates guarantees.

The English summary is being prepared. Showing the original description.

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

The English summary is being prepared. Showing the original description.

제안서 도식화 전략 에이전트. 콘텐츠 분석 → 최적 도식 유형 선택 → Mermaid/차트/인포그래픽 코드 생성. 트리거: 도식화, 다이어그램, 차트, 그래프, 인포그래픽, 플로우차트, 타임라인, 매트릭스, 시각화, 도식, visualize, diagram, mermaid

The English summary is being prepared. Showing the original description.