ot-project-description-builder
Build Milestone-Based OT Project Descriptions
OT teams need clear technical scope without unsupported authority or pricing conclusions. This skill builds validated DOCX descriptions and a separate cost-analysis handoff.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "ot-project-description-builder" from https://skillstore.io/skills/1102tools-dev-ot-project-description-builder.md and its manifest at https://skillstore.io/api/skills/1102tools-dev-ot-project-description-builder/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「ot-project-description-builder」を使用しています。 Create a Prototype OT description for a software pilot with approved authority but no useful TRL model.
期待される結果:
A decision summary uses observable maturity evidence, lists pending agreement facts, and proposes measurable software milestones before requesting approval.
「ot-project-description-builder」を使用しています。 Convert a priced SOW into an OT project description without carrying cost data into the agreement artifact.
期待される結果:
The resulting document preserves technical outcomes and acceptance evidence while excluding CLINs, rates, funding, staffing counts, and dollar amounts.
「ot-project-description-builder」を使用しています。 Reduce an approved prototype scope while keeping the technical baseline and milestone identifiers.
期待される結果:
The revision presents reduction choices with capability, evidence, schedule, and risk effects, then updates only the user-approved milestone structure.
セキュリティ監査
安全All 33 static findings are false positives. Archive access only validates local DOCX files, and reported command patterns are Markdown or a fixed local validator call. No malicious intent or prompt injection was found.
リスク要因
📁 ファイルシステムへのアクセス (6)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/1102tools-dev-ot-project-description-builder/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/1102tools-dev-ot-project-description-builder?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/1102tools-dev-ot-project-description-builder?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/1102tools-dev-ot-project-description-builder/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/1102tools-dev-ot-project-description-builder.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
1102tools-dev. (2026). ot-project-description-builder security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/1102tools-dev-ot-project-description-builder/audits/1BibTeX形式の引用
@techreport{1102tools-dev-1102tools-dev-ot-project-description-builder-2026,
author = {1102tools-dev},
title = {ot-project-description-builder security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/1102tools-dev-ot-project-description-builder/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "ot-project-description-builder security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "1102tools-dev"
date-released: "2026-08-24"
url: "https://skillstore.io/skills/1102tools-dev-ot-project-description-builder/audits/1"
identifiers:
- type: other
value: "skillstore:1102tools-dev-ot-project-description-builder:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Structure a New Prototype OT
Turn an approved prototype concept into phases, milestones, deliverables, and objective completion evidence.
Convert a Technical White Paper
Preserve approved technical facts while removing FAR artifact language, staffing details, and pricing content.
Reduce an Existing Scope
Compare scope reductions, show technical and schedule effects, and rebuild approved milestones without estimating savings.
これらのプロンプトを試す
Build an OT project description from this concept: [concept]. Ask for missing authority and scope facts before proposing milestones.
Convert the attached [document type] into an OT project description. Preserve settled technical decisions and exclude all pricing, funding, and FAR artifact content.
Using the confirmed [authority] and project outcome, propose phases and milestones with deliverables, objective completion evidence, dependencies, and pending decisions.
Revise the approved project description using these changes: [changes]. Preserve unaffected decisions, show impacts, obtain milestone approval, then generate and validate the DOCX.
ベストプラクティス
- Confirm statutory authority and participant facts before deriving scope.
- Approve the complete milestone structure before generating the DOCX.
- Run structural validation and visual page inspection after every document correction.
回避
- Do not ask the skill to choose authority or make participant-status determinations.
- Do not place costs, funding, labor rates, or the chat handoff inside the project description.
- Do not claim complete validation when rendering or page inspection was unavailable.
よくある質問
Which Other Transaction authorities does this skill support?
Can the skill select the correct authority?
Does the project description include cost estimates?
Is TRL required for every project?
What files does the skill produce?
How does the skill validate the final document?
開発者情報
作成者
1102tools-devライセンス
MIT
Skillstore リビジョン
r1
バージョンに関する注意
作者はバージョンを宣言していません。
参照
f574cb0caf5332a78ff4c1a3035cae6ad409aa6d
メンテナンスの新しさ
2026/8/25
利用状況
0 ダウンロード · 0 閲覧