ワンクリックでManusで任意のスキルを実行

isai-story-builder

Build and email ISAI sprint stories using the firm's standard story template. Use when asked to create, format, or email a sprint story, work item, or task for the ISAI team. Handles single stories or multi-story sprints. Fields include Story Title, Work Type, Description, Business Unit, Business Owner, Technical Owner, Platform, Hosting Model, Scope, Out of Scope, Assumptions, Dependencies, Data Classification, AI Model Involved, Vendor Risk Reviewed, Story Points, and Definition of Done. Triggers on phrases like "create a story", "build a sprint story", "write a work item", "format a story", "email a story", or any request to produce an ISAI-formatted story or task.

Manusで実行

概要

インストールコマンド

npx skills add https://github.com/OpieTaylor911/openclaw-skills --skill isai-story-builder

このコマンドをClaude Codeにコピー＆ペーストしてスキルをインストール

ソース

OpieTaylor911/openclaw-skills

スター0

フォーク0

更新日2026年3月30日 22:05

ファイルエクスプローラー

3 ファイル

SKILL.md

readonly

name

isai-story-builder

description

ISAI Story Builder

Produce correctly formatted ISAI sprint stories and optionally email them via msmtp.

Template Reference

See references/story-template.md for the full field reference, example story, and email format.

Template Fields

Jira Story Title:
Description:
Implementation:
Definition of Done (DOD):
Story Points:
Operations Readiness:
  - Will there be Operations Training?
  - Should an Operations Story be created?
  - Will Operations support the Completed Product?
Optional Notes:

See references/story-template.md for full field guidance and a complete example.

Workflow

1. Gather Inputs

Collect from the user (or infer from context):

Required: Jira Story Title, Description
Recommended: Implementation steps, Definition of Done, Story Points
Always include: Operations Readiness — all three questions must be answered or marked TBD
Optional Notes: use for dependencies, data classification, AI model involvement, risks, assumptions

If the user provides a rough description, extract and structure the fields. Do not ask for fields that can be reasonably inferred.

2. Build the Story

Use the exact field order from the template. Format as plain text with field labels followed by values. Lists use - item bullets.

For multiple stories, build each in sequence and clearly separate them (Story 1 of N, etc.).

3. Show Before Sending

Always display the formatted story before emailing. Confirm the user is satisfied.

4. Email (if requested)

Use msmtp (config at ~/.msmtprc):

printf "From: openclaw@isms-cloud.com\nTo: <recipient>\nSubject: [ISAI Story] <Title>\n\n<body>" | msmtp <recipient>

Default sender: openclaw@isms-cloud.com Ask the user for recipients if not specified.

Story Points Guide

Points	Effort
1–2	Small — communication, simple report
3	Medium — analysis + output
5	Large — multi-step, stakeholder coordination
8–13	Epic-sized — break into smaller stories

Definition of Done Defaults

Reporting / Operations:

Analysis completed using latest data
Output reviewed and approved
Delivered to intended audience
Feedback captured and documented
Action items tracked and assigned
Artifacts stored in governance repository

Communication:

Drafted and reviewed
Sent to all intended recipients
Delivery confirmed

Development:

Built and tested
Reviewed and merged
Documentation updated
Stakeholder sign-off obtained

このリポジトリの他の Skills

同じリポジトリ

ai-compliance

OpieTaylor911/openclaw-skills

AI compliance analysis for EU AI Act, ISO 42001, NIST AI RMF, GDPR, OECD, financial services regulations (SEC, FCA, FINRA, DORA, MiFID II), and other frameworks. Use when asked to generate a compliance checklist for an AI tool or use case, determine if a risk assessment is required, score an AI tool's risk level, identify where an AI tool or use case could run afoul of regulatory requirements, perform a gap analysis, recommend remediation steps, assess a vendor, draft an acceptable use policy, map training requirements, or review jurisdiction-specific AI rules. Triggers on phrases like "compliance checklist", "risk assessment", "risk score", "does this comply", "EU AI Act", "ISO 42001", "NIST AI RMF", "AI governance", "gap analysis", "vendor assessment", "acceptable use policy", "MNPI", "AI training requirements", or any request to evaluate an AI tool or use case for regulatory compliance or risk.

2026-03-300

goodwill-search

OpieTaylor911/openclaw-skills

Search ShopGoodwill.com for auction listings by keyword and display results with item images. Use when the user asks to search Goodwill, ShopGoodwill, or find items on goodwill auctions. Supports filtering by price range, filtering out accessories, and showing item images inline. Triggers on phrases like "search goodwill for", "find on shopgoodwill", "look up goodwill listings", "check goodwill for", or any request to browse/scrape ShopGoodwill auction listings.

2026-03-300

legal

OpieTaylor911/openclaw-skills

Think through any legal situation like a lawyer. Issue spotting, jurisdiction, risk assessment, actionable conclusions.

2026-03-300

mermaid-diagrams

OpieTaylor911/openclaw-skills

Generate architecture diagrams (network, system, cloud, microservices) and sequence diagrams (API flows, auth flows, data flows) as PNG files using Mermaid. Use when asked to create, draw, or diagram anything including system architecture, network topology, cloud infrastructure, API request flows, authentication flows, CI/CD pipelines, database flows, or any other technical diagram. Triggers on phrases like "create a diagram", "draw", "diagram this", "architecture diagram", "sequence diagram", "flow diagram", "network diagram", "system design diagram".

2026-03-300

model-audit

OpieTaylor911/openclaw-skills

Monthly LLM stack audit — compare your current models against latest benchmarks and pricing from OpenRouter. Identifies potential savings, upgrades, and better alternatives by category (reasoning, code, fast, cheap, vision). Use for optimizing AI costs and staying on the frontier.

2026-03-300

ソース

OpieTaylor911

OpieTaylor911/openclaw-skills

GitHub リポジトリを開く Creator のリポジトリを見る

インストールコマンド

ダウンロード

Manusで実行

役立つ用途SOC

プロジェクト管理専門家ビジネス・金融業務職13-1082L4

name

isai-story-builder

description

ISAI Story Builder

Produce correctly formatted ISAI sprint stories and optionally email them via msmtp.

Template Reference

See references/story-template.md for the full field reference, example story, and email format.

Template Fields

Jira Story Title:
Description:
Implementation:
Definition of Done (DOD):
Story Points:
Operations Readiness:
  - Will there be Operations Training?
  - Should an Operations Story be created?
  - Will Operations support the Completed Product?
Optional Notes:

See references/story-template.md for full field guidance and a complete example.

Workflow

1. Gather Inputs

Collect from the user (or infer from context):

Required: Jira Story Title, Description
Recommended: Implementation steps, Definition of Done, Story Points
Always include: Operations Readiness — all three questions must be answered or marked TBD
Optional Notes: use for dependencies, data classification, AI model involvement, risks, assumptions

If the user provides a rough description, extract and structure the fields. Do not ask for fields that can be reasonably inferred.

2. Build the Story

Use the exact field order from the template. Format as plain text with field labels followed by values. Lists use - item bullets.

For multiple stories, build each in sequence and clearly separate them (Story 1 of N, etc.).

3. Show Before Sending

Always display the formatted story before emailing. Confirm the user is satisfied.

4. Email (if requested)

Use msmtp (config at ~/.msmtprc):

printf "From: openclaw@isms-cloud.com\nTo: <recipient>\nSubject: [ISAI Story] <Title>\n\n<body>" | msmtp <recipient>

Default sender: openclaw@isms-cloud.com Ask the user for recipients if not specified.

Story Points Guide

Points	Effort
1–2	Small — communication, simple report
3	Medium — analysis + output
5	Large — multi-step, stakeholder coordination
8–13	Epic-sized — break into smaller stories

Definition of Done Defaults

Reporting / Operations:

Analysis completed using latest data
Output reviewed and approved
Delivered to intended audience
Feedback captured and documented
Action items tracked and assigned
Artifacts stored in governance repository

Communication:

Drafted and reviewed
Sent to all intended recipients
Delivery confirmed

Development:

Built and tested
Reviewed and merged
Documentation updated
Stakeholder sign-off obtained