using-agent-skills

Discovers and routes tasks to phase-specific engineering workflow skills.

5|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/PHenrique07/Sementis-IFSP-Pirituba --skill using-agent-skills-phenrique07
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/PHenrique07/Sementis-IFSP-Pirituba/tree/main/.github/skills/using-agent-skills
Command: npx skills add https://github.com/PHenrique07/Sementis-IFSP-Pirituba --skill using-agent-skills-phenrique07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When starting a development task, it is often unclear which engineering workflow applies, leading to skipped specs, missing verification, and inconsistent quality. This meta-skill maps any incoming task to the correct skill based on its development phase. ## Core Features & Use Cases - Skill Discovery Decision Tree: Routes tasks to the right skill (e.g., spec-driven-development, test-driven-development, debugging-and-error-recovery) based on the current development phase. - Core Operating Behaviors: Enforces six non-negotiable behaviors including surfacing assumptions, managing confusion, pushing back on bad ideas, and verifying results. - Lifecycle Sequencing: Defines the typical skill order for a complete feature, from interview-me through shipping-and-launch. - Use Case: A developer receives a vague feature request. The meta-skill routes them to interview-me, then spec-driven-development, then incremental-implementation, ensuring no critical step is skipped. ## Quick Start Ask the agent to determine which skill applies to your current task, such as "which skill should I use to fix this broken API endpoint?"

Frequently Asked Questions about using-agent-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right skill for a development task?▼

Identify the development phase of your task and follow the decision tree: new features route to spec-driven-development, broken behavior routes to debugging-and-error-recovery, and test work routes to test-driven-development. When in doubt, start with a spec.

What is the typical skill sequence for a complete feature?▼

The lifecycle runs from interview-me and idea-refine through spec-driven-development, planning-and-task-breakdown, incremental-implementation, test-driven-development, code-review-and-quality, and finally shipping-and-launch. Not every task needs every skill.

Can multiple skills apply to a single task?▼

Yes, multiple skills can apply in sequence. A feature implementation might chain idea-refine, spec-driven-development, planning-and-task-breakdown, incremental-implementation, test-driven-development, and code-review-and-quality.

When should I skip the spec-driven-development skill?▼

Simple bug fixes can skip the spec phase and use only debugging-and-error-recovery, test-driven-development, and code-review-and-quality. Non-trivial tasks without a spec should always begin with spec-driven-development.

What verification is required before a task is complete?▼

Every skill includes a verification step requiring concrete evidence such as passing tests, build output, or runtime data. The project-wide Definition of Done requires tests passing, no regressions, runtime verification, and updated docs.