This skill should be used when creating structured feature specifications and task tracking documents. It provides standardized templates for spec.md, tasks.md, and component.md in the knowledge-base/ directory.
From soleurnpx claudepluginhub jikig-ai/soleur --plugin soleurThis skill uses the workspace's default tool permissions.
Provides templates for structured feature specifications.
soleur:brainstorm to create spec.mdsoleur:plan to create tasks.mdknowledge-base/project/specs/Use this template for feature specifications:
# Feature: [name]
## Problem Statement
[What problem are we solving?]
## Goals
- [What we want to achieve]
## Non-Goals
- [What is explicitly out of scope]
## Functional Requirements
### FR1: [name]
[User-facing behavior]
## Technical Requirements
### TR1: [name]
[Architecture, performance, security considerations]
Use this template for task tracking:
# Tasks: [name]
## Phase 1: Setup
- [ ] 1.1 Task description
## Phase 2: Core Implementation
- [ ] 2.1 Main task
- [ ] 2.1.1 Subtask if needed
## Phase 3: Testing
- [ ] 3.1 Task description
Each feature gets its own directory:
knowledge-base/project/specs/feat-<name>/
spec.md # Requirements (FR/TR)
tasks.md # Phased task checklist
knowledge-base/project/specs/feat-user-auth/spec.md using the template abovetasks.md using the templateUse this template for project overview component documentation in knowledge-base/project/components/:
---
component: <component-name>
updated: YYYY-MM-DD
primary_location: <path/to/component/>
related_locations:
- <other/path>
---
# <Component Name>
[One paragraph - what this component does]
## Purpose
[Why this component exists and its role in the system]
## Responsibilities
- [Key responsibility 1]
- [Key responsibility 2]
## Key Interfaces
[Public APIs, entry points, exported types]
## Data Flow
[How data enters and exits this component - include mermaid diagram if helpful]
## Dependencies
- **Internal**: [other components it uses]
- **External**: [third-party packages]
## Examples
[Usage examples with code]
## Related Files
- `path/to/file` - [description]
## See Also
- [constitution.md](../constitution.md) for coding conventions
- [Related component](./related.md)
| Field | Required | Description |
|---|---|---|
component | Yes | Kebab-case component name |
updated | Yes | Date last updated (YYYY-MM-DD) |
primary_location | Yes | Main directory/file path |
related_locations | No | Additional paths if component spans directories |
status | No | active, deprecated (default: active) |
knowledge-base/project/components/<name>.md