janjaali-agent-plugin
v1.0.0Reusable, agent-agnostic skills: general code and markdown conventions, Scala ADR compliance, and a spec-driven development workflow.
By janjaaliLicense: MIT1 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Agent Plugins
- Parsed components
- 4 skill or MCP entries
- Source updated
- Sep 11, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Get the plugin
git clone https://github.com/janjaali/agent-pluginClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.
This listing currently publishes only the generic Agent Plugins format. Automatic install commands for other clients are not generated yet.
Plugin files
├── plugin.json├── skills/adr-compliance/SKILL.md├── skills/code-structure-and-documentation/SKILL.md├── skills/markdown-formatting/SKILL.md└── skills/spec-workflow/SKILL.md
Included Skills4
Enforces the active Scala ADR set from this plugin's adr/ directory, covering testing conventions, Scala file hygiene, immutable sequence literal style, HOCON comment syntax, and exhaustive matching rules. Applies when writing or reviewing Scala code and related configuration.
Enforces structure, documentation, comment, and ~80-column line-width conventions org-wide for generated or edited source code. Applies to all languages and repos, regardless of any more specific language convention.
Enforces markdown formatting conventions org-wide — no manual line-wrapping in prose. Applies to all markdown files (SPEC.md, ADRs, READMEs, docs) regardless of repo or language.
**WORKFLOW SKILL** — Interview the user about specification changes and generate one or more standalone SPEC.md documents (one per spec folder) that serve as a high-level overview of the component or process: contract, behavior, and business intent, captured as user stories and EARS-notation acceptance criteria. Technical architecture, diagrams, and implementation-level detail live in companion documents (DESIGN.md, DOMAIN.md, DATABASE.md, KAFKA.md, CONVENTIONS.md). The agent uses SPEC.md plus companion documents together for planning and code generation.
Plugin manifests1
{
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
"name": "janjaali-agent-plugin",
"version": "1.0.0",
"description": "Reusable, agent-agnostic skills: general code and markdown conventions, Scala ADR compliance, and a spec-driven development workflow.",
"author": {
"name": "janjaali",
"email": "[email protected]"
},
"repository": "https://github.com/janjaali/agent-plugin",
"license": "MIT",
"keywords": [
"conventions",
"adr",
"spec-driven-development",
"scala"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[janjaali-agent-plugin on Agent Plugins Marketplace](https://pluginsmp.com/plugins/janjaali-agent-plugin)