Help us improve
Share bugs, ideas, or general feedback.
From tech-lead
Generate structured feature specifications with Business Rules (BR), User Stories (US), and Acceptance Criteria (AC).
npx claudepluginhub ruslan-korneev/claude-plugins --plugin tech-leadHow this skill is triggered — by the user, by Claude, or both
Slash command
/tech-lead:feature-specificationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate structured feature specifications with Business Rules (BR), User Stories (US), and Acceptance Criteria (AC).
Generates structured feature specifications with demoable units, functional requirements, and proof artifacts. Use when defining what to build before writing code.
Develops feature ideas into structured specifications via guided conversation with architectural analysis, UX input, and decomposition for large features.
Generates structured feature specifications via collaborative PM/BA interview. Challenges scope, proposes options at decisions, outputs epic/feature hierarchy in .lattice/requirements/.
Share bugs, ideas, or general feedback.
Generate structured feature specifications with Business Rules (BR), User Stories (US), and Acceptance Criteria (AC).
Use this skill when the user wants to:
Trigger phrases:
Features are organized into 6 phases based on their role:
| Phase | Prefix | Description |
|---|---|---|
| Core | core- | Fundamental entities (users, products, orders) |
| Workflow | workflow- | Business processes (checkout, approval) |
| Lifecycle | lifecycle- | State transitions, notifications |
| Analytics | analytics- | Reporting, metrics, dashboards |
| Integration | integration- | External APIs, third-party services |
| UI | ui- | User interface components |
Each requirement uses a standardized identifier:
Where:
XXX — 3-letter domain code (USR, ORD, PAY, etc.)YYY — Sequential number (001, 002, ...)## BR-XXX-001: Business Rule Title
**Description**: What this rule defines
**Rationale**: Why this rule exists
### User Stories
#### US-XXX-001: As a [role], I want [goal]
**Acceptance Criteria:**
- [ ] AC-XXX-001: Given [context], when [action], then [outcome]
- [ ] AC-XXX-002: Given [context], when [action], then [outcome]
For existing codebases:
For new projects:
docs/technical-requirements/features/
├── README.md # Index with dependency graph
├── 00-template.md # Feature template
├── core-01-user-management.md # Core features
├── core-02-authentication.md
├── workflow-01-order-creation.md # Workflow features
├── lifecycle-01-notifications.md # Lifecycle features
├── analytics-01-reports.md # Analytics features
├── integration-01-email.md # Integration features
└── ui-01-admin-panel.md # UI features
<!-- manual -->
This content is preserved during regeneration
<!-- /manual -->
draft — File exists, no code yetin_progress — Code exists, tests failingcompleted — Code + tests passing