القائمة
Analyze and enhance Jira user stories with complete, implementation-ready technical detail.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when performing a cybersecurity audit, security review, OWASP Top 10 compliance check, vulnerability assessment, or preparing for a penetration test on a Node.js/Express/React application.
Run N feature tasks in parallel, each in its own worktree, following the full specboot pipeline (enrich → new → ff → apply → verify). Stops after verify — no archive, no commit, no cleanup. Explicit task arguments override `parallel-tasks.md`; file is fallback only.
Use when the user requests an adversarial review, red-team review, devil's advocate check, or independent verification pass before archiving an OpenSpec change.
Use when the user asks "show me X", "demo X", "walk me through X", "how X works" or requests a live feature demonstration from a spec, feature or ticket.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Analyze and synchronize agent skill exposure after ai-specs skill changes (additions, removals, renames). Use when skills are added/removed in ai-specs and .claude/skills and .cursor/skills must stay aligned through symlinks.
| name | enrich-us |
| description | Analyze and enhance Jira user stories with complete, implementation-ready technical detail. |
| author | LIDR.co |
| version | 1.0.0 |
Use it when this workflow is required in the project.
Please analyze and fix the Jira ticket: $ARGUMENTS.
Follow these steps:
tmp/ folder at the project root (create the folder if it doesn't exist). Name the file <ticket-id>-enriched-us.md (e.g., LTI-42-enriched-us.md). The tmp/ folder is already in .gitignore.