Closing the intent-to-code chasm - specification-driven development with BDD verification chain
Overall
score
96%
Does it follow best practices?
Validation for skill structure
#!/usr/bin/env bash
# SessionStart hook: restore IIKit feature context after /clear
#
# Outputs feature context as additionalContext so Claude knows
# where the user is in the IIKit workflow after a context reset.
SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
source "$SCRIPT_DIR/common.sh"
REPO_ROOT=$(get_repo_root 2>/dev/null) || exit 0
# Check if this is an IIKit project
if [[ ! -f "$REPO_ROOT/CONSTITUTION.md" ]] && [[ ! -d "$REPO_ROOT/.specify" ]]; then
exit 0
fi
# Try to detect active feature
FEATURE=""
FEATURE=$(read_active_feature "$REPO_ROOT" 2>/dev/null) || true
if [[ -z "$FEATURE" ]]; then
# No active feature — just confirm IIKit is initialized
echo "IIKit project. Run /iikit-core status to see current state."
exit 0
fi
STAGE=$(get_feature_stage "$REPO_ROOT" "$FEATURE")
FEATURE_DIR="$REPO_ROOT/specs/$FEATURE"
# Build context summary
echo "IIKit active feature: $FEATURE (stage: $STAGE)"
case "$STAGE" in
specified)
echo "Next: /iikit-02-clarify or /iikit-03-plan"
;;
planned)
echo "Next: /iikit-04-checklist or /iikit-06-tasks"
;;
tasks-ready)
echo "Next: /iikit-07-analyze or /iikit-08-implement"
;;
implementing-*)
echo "Next: /iikit-08-implement (resume)"
;;
complete)
echo "All tasks complete. /iikit-09-taskstoissues to export."
;;
esacInstall with Tessl CLI
npx tessl i tessl-labs/intent-integrity-kit@2.3.5rules
skills
iikit-00-constitution
scripts
iikit-01-specify
iikit-02-clarify
iikit-03-plan
iikit-04-checklist
scripts
dashboard
iikit-05-testify
iikit-06-tasks
iikit-07-analyze
iikit-08-implement
iikit-09-taskstoissues
iikit-bugfix
scripts
iikit-core
scripts
bash
dashboard
powershell