菜单
Generate technical specifications from approved functional specs (Azure DevOps Epic hierarchies) and publish as wiki pages. Use after functional approval to create implementation-ready technical documentation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Design ASP.NET Core minimal API request and response contracts. Use for DTO shapes, route and verb decisions, OpenAPI metadata, and compatibility planning before implementation.
Define focused tests for ASP.NET Core minimal APIs. Use for endpoint branch coverage, contract assertions, regression planning, and choosing the narrowest useful verification command.
Design EF Core schema changes, constraints, and migrations for the backend data model. Use for entity updates, indexes, uniqueness rules, cascade behavior, and migration planning.
Design and implement the delegated Graph sync pipeline from fetch through normalization, upsert, and metrics recompute. Use for user-initiated registrations or attendance sync, idempotency, and atomic recomputation.
Define deployment safeguards, environment protections, and rollback readiness for CI/CD releases. Use when adding or reviewing release jobs, promotion controls, or recovery plans.
Apply email and domain normalization plus session and series metric rules, including W1/W2 warm-account logic and internal-domain exclusion. Use for domain logic changes, recompute behavior, and mandatory unit-test coverage.
| name | technical-spec-generation |
| description | Generate technical specifications from approved functional specs (Azure DevOps Epic hierarchies) and publish as wiki pages. Use after functional approval to create implementation-ready technical documentation. |
| argument-hint | Provide the Epic ID to generate a technical specification for, or ask to review/update an existing tech spec. |
The calling agent must provide:
Use these values for all MCP calls, wiki publishing, and link generation. This skill defines generic generation rules only; do not hardcode repository-specific Azure DevOps targets here.
Active + has approval comment + no review:ready tag| Type | Canonical fields |
|---|---|
| Epic | Description |
| Feature | Description (includes embedded AC) |
| User Story | Description + Microsoft.VSTS.Common.AcceptanceCriteria |
| Artifact | Format | Path |
|---|---|---|
| Tech spec wiki page | Markdown | .github\skills\technical-spec-generation\templates\technical-spec.md |
| Link comment | Markdown | .github\skills\technical-spec-generation\templates\tech-spec-link-comment.md |
| Regeneration summary | Markdown | .github\skills\technical-spec-generation\templates\regeneration-summary-comment.md |
Rules: load template first; preserve metadata block + heading order; reject output with unresolved placeholders.
Active, has approval comment, no review:ready. If techspec:stale, warn and proceed only on confirmed understanding./Tech-Specs/[Epic-ID]-[Slugified-Title] (e.g. /Tech-Specs/356-Session-Import-from-CSV). Use MCP wiki_create_or_update_page with caller-provided wikiIdentifier and project.techspec:stale; if regeneration, add second comment (regeneration template).techspec:stale present)techspec:stale.Active + approval comment + wiki-link commentreview:ready / techspec:stale remaining