Claude Agent Skill · by Github

Create Github Issues For Unmet Specification Requirements

The skill analyzes specification files to identify unimplemented requirements, checks the codebase and existing GitHub issues to avoid duplicates, and automatic

Install
Terminal · npx
$npx skills add https://github.com/github/awesome-copilot --skill create-github-issues-for-unmet-specification-requirements
Works with Paperclip

How Create Github Issues For Unmet Specification Requirements fits into a Paperclip company.

Create Github Issues For Unmet Specification Requirements drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.

S
SaaS FactoryPaired

Pre-configured AI company — 18 agents, 18 skills, one-time purchase.

$27$59
Explore pack
Source file
SKILL.md35 lines
Expand
---name: create-github-issues-for-unmet-specification-requirementsdescription: 'Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.'--- # Create GitHub Issues for Unmet Specification Requirements Create GitHub Issues for unimplemented requirements in the specification at `${file}`. ## Process 1. Analyze specification file to extract all requirements2. Check codebase implementation status for each requirement3. Search existing issues using `search_issues` to avoid duplicates4. Create new issue per unimplemented requirement using `create_issue`5. Use `feature_request.yml` template (fallback to default) ## Requirements - One issue per unimplemented requirement from specification- Clear requirement ID and description mapping- Include implementation guidance and acceptance criteria- Verify against existing issues before creation ## Issue Content - Title: Requirement ID and brief description- Description: Detailed requirement, implementation method, and context- Labels: feature, enhancement (as appropriate) ## Implementation Check - Search codebase for related code patterns- Check related specification files in `/spec/` directory- Verify requirement isn't partially implemented