「writer」の検索結果

Reference batch writer compatibility gate during the DESIGN.md Core v2 catalog cutover.

日本語の概要は準備中です。原文の説明を表示しています。

Product Requirements Document writing - PRD templates, MoSCoW prioritization, user personas, competitive analysis, feature specs, acceptance criteria, risk assessment

日本語の概要は準備中です。原文の説明を表示しています。

Use when module planning and source coverage are done and the run needs writer-ready per-module packs.

日本語の概要は準備中です。原文の説明を表示しています。

Writing self-loop for surveys: run the strict section-quality gate, then rewrite only the failing `sections/*.md` files until the report is PASS.

日本語の概要は準備中です。原文の説明を表示しています。

Use when approved tutorial context packs exist and the run needs the final article-first tutorial deliverable.

日本語の概要は準備中です。原文の説明を表示しています。

Use when `paper-review` has claims plus evidence gaps and needs the final referee-style report.

日本語の概要は準備中です。原文の説明を表示しています。

Use when `evidence-review` needs an operational protocol before screening and extraction.

日本語の概要は準備中です。原文の説明を表示しています。

Write `output/DRAFT.md` (or `output/SNAPSHOT.md`) from an approved outline and evidence packs, using only verified citation keys from `citations/ref.bib`.

日本語の概要は準備中です。原文の説明を表示しています。

Write survey prose into per-section files under `sections/` so each unit can be QA'd independently before merging.

日本語の概要は準備中です。原文の説明を表示しています。

Use when `evidence-review` has completed extraction and needs a bounded narrative synthesis.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a `research-brief` workspace has a small paper set plus outline and needs a compact reader-facing briefing instead of a full survey.

日本語の概要は準備中です。原文の説明を表示しています。

Extract per-subsection “anchor facts” (NO PROSE) from evidence packs so the writer is forced to include concrete numbers/benchmarks/limitations instead of generic summaries.

日本語の概要は準備中です。原文の説明を表示しています。

Curate reader-facing survey tables for the Appendix (clean layout + high information density), using only in-scope evidence and existing citation keys.

日本語の概要は準備中です。原文の説明を表示しています。

Seed `outline/claim_evidence_matrix.md` from outline+notes; claim-matrix-rewriter rewrites it later from evidence packs.

日本語の概要は準備中です。原文の説明を表示しています。

Write the survey's front matter files (Abstract, Introduction, Related Work, Discussion, Conclusion) in paper voice, with high citation density and a single evidence-policy paragraph.

日本語の概要は準備中です。原文の説明を表示しています。

Synthesize the shortlist into a discussion-ready research idea brainstorm memo, writing `output/REPORT.md`, `output/APPENDIX.md`, and `output/REPORT.json`.

日本語の概要は準備中です。原文の説明を表示しています。

Rewrite `outline/claim_evidence_matrix.md` as a projection/index of evidence packs (NO PROSE), so claims/axes are driven by `outline/evidence_drafts.jsonl` rather than outline placeholders.

日本語の概要は準備中です。原文の説明を表示しています。

Write H2 chapter lead blocks (`sections/S<sec_id>_lead.md`) that preview the chapter's comparison lens and connect its H3 subsections, without adding new facts.

日本語の概要は準備中です。原文の説明を表示しています。

Use Sep for high-performance separated-value parsing and writing in .NET, including delimiter inference, explicit parser/writer options, and low-allocation row/column workflows. USE FOR: delimited data needs are performance-sensitive and allocation-aware; project needs explicit control over separator inference, escaping, trimming, and header behavior;. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

日本語の概要は準備中です。原文の説明を表示しています。

Write LaTeX ML/AI review articles for arXiv using the IEEEtran template and verified BibTeX citations. Use when writing, planning, or continuing an arXiv review/survey paper, or when validating and repairing citations in an existing LaTeX project.

日本語の概要は準備中です。原文の説明を表示しています。

Read a real .pptx using text extraction, OOXML inspection, slide rendering, OCR, visual inventory, and vision-capable screenshot review; then write academic speaker notes grounded in every visible slide element, generate a complete display-version document, and inject clean notes into the PowerPoint notes pane. Use when the user wants speaker notes, presenter notes, a speech script, narration, or annotated notes for an existing PowerPoint deck, especially when slides contain images, charts, tables, SmartArt, axes, legends, or screenshot text.

日本語の概要は準備中です。原文の説明を表示しています。

Write SEO-optimized blog posts, landing pages, and long-form page copy following Google's E-E-A-T and Helpful Content guidelines. Handles new content creation from a keyword, topic, or brief, and full-page rewrites. Use when asked to "write a blog post", "create a landing page", "write content about X", "content for keyword X", "draft an article", "blog post about", "landing page for", "service page", "product page copy", "rewrite this page", "how-to guide", or "listicle". NOT for analyzing/auditing existing content (seo-geo-optimizer, content-quality-auditor), title tags or meta descriptions (meta-tags-optimizer), or keyword expansion (keyword-research) — those skills own their triggers.

日本語の概要は準備中です。原文の説明を表示しています。

Generates English pull request titles and bodies by comparing the current branch with main. Use when the user asks to draft PR content, summarize branch changes, or produce a PR title/body from git diff.

日本語の概要は準備中です。原文の説明を表示しています。

Repair a repeatedly failing Standard paper section from repair_queue.json, or generate an explicitly requested legacy/quickstart scaffold. Do not use it as the formal paper writer.

日本語の概要は準備中です。原文の説明を表示しています。