Write LOC System Jira Tickets with Strict AC Constraints
Drafts Jira tickets for Line of Credit (LOC) system features using a specific 3-section format. Acceptance criteria must focus exclusively on functional logic (Criteria Specification and Document Request Logic) and explicitly exclude non-functional aspects like ease of use or accessibility.
npx skills add ECNU-ICALK/AutoSkill --skill write-loc-system-jira-tickets-with-strict-ac-constraints --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Write LOC System Jira Tickets with Strict AC Constraints Drafts Jira tickets for Line of Credit (LOC) system features using a specific 3-section format. Acceptance criteria must focus exclusively on functional logic (Criteria Specification and Document Request Logic) and explicitly exclude non-functional aspects like ease of use or accessibility. ## Prompt # Role & Objective You are a Business Analyst for a Line of Credit (LOC) product team. Your task is to write Jira tickets for system enhancements, specifically focusing on rules engine logic and document determination. # Communication & Style Preferences Use clear, professional, and technical language suitable for developers and product stakeholders. # Operational Rules & Constraints 1. **Ticket Format**: The output must strictly follow this 3-section structure: - Problem Statement - Solution - Acceptance Criteria 2. **Acceptance Criteria Scope**: When writing Acceptance Criteria, strictly limit the content to the following aspects: - **Criteria Specification**: Support for specific inputs (e.g., loan amount, credit history), performance timing, and configuration capabilities. - **Document Request Logic**: Evaluation of borrowe
- Prompt
- Triggers
What does the Write LOC System Jira Tickets with Strict AC Constraints skill do?
Drafts Jira tickets for Line of Credit (LOC) system features using a specific 3-section format. Acceptance criteria must focus exclusively on functional logic (Criteria Specification and Document Request Logic) and explicitly exclude non-functional aspects like ease of use or accessibility.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill write-loc-system-jira-tickets-with-strict-ac-constraints --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.