菜单
Async advisory story verification skill. Phase 3.2 adds the manual /story-verification workflow on top of the Phase 3.1 read-only verify-stories CLI front door.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Deploy files to the Tesseract Academy WordPress site on Cloudways via SSH/SCP
Write B2B cold emails and follow-up sequences that get replies. Adapted from coreyhaines31/marketingskills for the Tesseract Automation Engine. Used by the Sales Director agent and any outreach mission. Must read product-marketing-context before drafting.
How to use the Elastic Email integration for fetching engagement data, bounces, and unsubscribes
Create or optimize email sequences, drip campaigns, and lifecycle email flows. Adapted from coreyhaines31/marketingskills for the Tesseract Automation Engine. Used by the Sales Director agent for nurture sequences and by the Marketing Team for welcome/onboarding flows. Must read product-marketing-context before drafting.
Agent protocol for reading, interpreting, and updating marketing funnel documentation.
State-machine driven iterative planning and execution for complex coding tasks. Cycle: Explore → Plan → Execute → Reflect → Validate → Close / Re-plan. Filesystem as persistent memory. Use for multi-file tasks, migrations, refactoring, failed tasks, audit remediations, or anything non-trivial.
| name | story-verification |
| description | Async advisory story verification skill. Phase 3.2 adds the manual /story-verification workflow on top of the Phase 3.1 read-only verify-stories CLI front door. |
Use this skill after Agent A has already completed its blocking work and you need deeper advisory verification against stories, annotations, and declared verification obligations.
read-only with respect to source code and reports/user_story_audit/story_registry.json.advisory: it supplements Agent A's blocking validation_refs and broken_evidence_chain contract; it does not replace or block it.plans/<plan_id>/verification_strategy.yaml, reports/user_story_audit/story_registry.json, and host code/test files.reports/story_verification/*.yaml plus structured JSONL entries under reports/errors/.scripts/extract_annotations.mjs parses @planner:* annotations from real code/test files.scripts/verify_coverage.mjs applies the status-scoped story coverage checks.scripts/verify_obligations.mjs checks that declared how_verified obligations match real evidence.scripts/report_generator.mjs validates and writes verification_report.yaml outputs.prolog/story_rules.pl carries the inventory-authorized Agent B story invariants that story-facing verification commands load on top of the shared planner ontology.../iterative-planner/scripts/verify_stories.mjs is the read-only Agent B CLI entry point surfaced via planner verify-stories.planner verify-stories --all now emits an aggregate fleet summary and skips legacy markdown-only plans by default; --staged --skip-legacy extends the same tolerance to mixed staged batches.../iterative-planner/scripts/hooks/post_commit_story_verification.mjs is the optional post-commit launcher installed by planner install-hook story-verification and gated by .agent/version.json.../../workflows/story-verification.md is the manual workflow front door for operators using the shipped CLI.tests/test_story_verification.mjs is the focused scaffold proof bundle.docs/ci/.