verifyfeat
Verify feature completion by checking child tasks and running verify target
What this skill does
# Verify Feature Completion
Verifies that a beads feature is complete by:
1. Checking all child tasks are closed
2. Executing the build system `verify` target
3. Running comprehensive validation including integration tests
## Usage
```bash
# Verify feature
/bkff:verifyfeat --issue=beads-abc123
# Output as JSON
/bkff:verifyfeat --issue=beads-abc123 --format=json
```
## Verification Process
```
┌─────────────────────────────────────────────────────────┐
│ CHECK ACCEPTANCE CRITERIA │
│ (must be defined on the feature) │
└─────────────────────┬───────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────┐
│ CHECK CHILD TASKS │
│ (all must be in 'closed' status) │
└─────────────────────┬───────────────────────────────────┘
│
┌──────────┴──────────┐
│ │
▼ ▼
┌─────────────┐ ┌─────────────┐
│ All Closed │ │ Open Tasks │
└──────┬──────┘ └──────┬──────┘
│ │
▼ ▼
┌─────────────┐ ┌─────────────┐
│ Run verify │ │ FAIL │
│ target │ │ (list open) │
└──────┬──────┘ └─────────────┘
│
▼
┌─────────────────────────────────────────────────────┐
│ VERIFICATION RESULT │
│ (pass/fail based on verify target exit code) │
└─────────────────────────────────────────────────────┘
```
## What Gets Checked
The `verify` target should run comprehensive validation:
| Check Type | Description |
|------------|-------------|
| Integration Tests | Cross-component tests |
| Feature Documentation | Feature-level docs complete |
| API Contracts | API compatibility verified |
| Performance | Performance benchmarks (if defined) |
| All validate checks | Tests, quality, security, standards |
## Output
### With Open Child Tasks
```
Warning: Feature has 2 open child task(s)
Verification Result
─────────────────────────────────────
Issue: beads-abc123
Target: verify
✗ Verification failed
Summary:
Failures:
beads:-: [standards] Feature has 2 open child task(s) that must be completed first
```
### Verification Passed
```
Info: Verifying feature: beads-abc123
Verification Result
─────────────────────────────────────
Issue: beads-abc123
Target: verify
✓ Verification passed
```
## Requirements
- Beads feature must have acceptance criteria defined
- All child tasks must be in 'closed' status
- Build system must have a `verify` target in Makefile
- `bd` CLI must be available
## Exit Codes
- `0` - Verification passed
- `1` - Verification failed (open children or verify target failed)
- `2` - Missing acceptance criteria
- `3` - Missing verify target
## Related Skills
- `/bkff:verifytask` - Verify task completion
- `/bkff:verifyepic` - Verify epic completion
## Implementation
```bash
#!/usr/bin/env bash
set -euo pipefail
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
PLUGIN_DIR="$(dirname "$(dirname "$SCRIPT_DIR")")"
source "$PLUGIN_DIR/lib/common.sh"
source "$PLUGIN_DIR/lib/verification.sh"
# Parse arguments
issue_id=""
format="human"
for arg in "$@"; do
case "$arg" in
--issue=*) issue_id="${arg#--issue=}" ;;
--format=json) format="json" ;;
--format=human) format="human" ;;
--json) format="json" ;;
esac
done
# Validate prerequisites
require_worktree
require_bd
if [[ -z "$issue_id" ]]; then
error_exit "Issue ID required. Use --issue=<id>"
fi
# Run verification
result=$(verify_feature "$issue_id")
# Output based on format
if [[ "$format" == "json" ]]; then
echo "$result"
else
echo "$result" | print_verification_result
fi
# Exit with appropriate code
status=$(echo "$result" | jq -r '.status')
[[ "$status" == "pass" ]]
```
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.