Skills gjalla-spec
📦
gjalla-spec
Content revision r1 Safe ⚙️ External commands
Create Production-Ready Software Specifications
Complex features fail when requirements, architecture effects, and verification criteria remain unclear. This skill guides agents through research and produces an implementation-ready Gjalla specification.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "gjalla-spec" from https://skillstore.io/skills/gjalla-gjalla-spec.md and its manifest at https://skillstore.io/api/skills/gjalla-gjalla-spec/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "gjalla-spec". Plan account deletion across authentication, billing, and analytics services.
Expected outcome:
- Problem: Account deletion behavior is inconsistent across services.
- Goal: Remove personal data while preserving legally required billing records.
- Approach: Coordinate deletion events, retention rules, retries, audit records, and service ownership.
- Verification: Test complete deletion, partial failures, retries, retention exceptions, and rollback.
Using "gjalla-spec". Specify a gradual migration from synchronous notifications to a queue.
Expected outcome:
- Non-goal: Replacing notification providers is outside this migration.
- Architecture delta: Producers publish durable jobs while workers handle delivery and retries.
- Dependencies: Queue infrastructure, observability, idempotency keys, and deployment sequencing.
- Rollback: Route producers back to synchronous delivery while safely draining queued jobs.
Security Audit
Safev1 • 8/11/2026 Open versioned report
The only static finding is a false positive caused by Markdown backticks around a Gjalla CLI command. The prompt contains no executable code, prompt injection, or malicious intent.
1
Files scanned
30
Lines analyzed
0
Review items
0
False positives ignored
Risk Factors
⚙️ External commands (1)
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/gjalla-gjalla-spec/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/gjalla-gjalla-spec?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/gjalla-gjalla-spec?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/gjalla-gjalla-spec/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/gjalla-gjalla-spec.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
gjalla. (2026). gjalla-spec security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/gjalla-gjalla-spec/audits/1BibTeX citation
@techreport{gjalla-gjalla-gjalla-spec-2026,
author = {gjalla},
title = {gjalla-spec security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/gjalla-gjalla-spec/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "gjalla-spec security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "gjalla"
date-released: "2026-08-11"
url: "https://skillstore.io/skills/gjalla-gjalla-spec/audits/1"
identifiers:
- type: other
value: "skillstore:gjalla-gjalla-spec:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: Medium 55
Architecture
85
Maintainability
87
Content
65
Community
91
Spec Compliance
What You Can Build
Plan a Cross-Service Feature
Map architecture effects, data flows, dependencies, rollback steps, and tests before changing multiple services.
Define Acceptance Criteria
Turn a product problem into explicit goals, non-goals, observable behaviors, and acceptance tests.
Prepare an Implementation Handoff
Create a concise reference specification that gives delivery teams shared technical and verification guidance.
Try These Prompts
Draft a Feature Specification
Create a Gjalla specification for [feature]. Research the current architecture, ask necessary questions, and define goals, requirements, approach, tests, dependencies, and rollback.
Clarify an Ambiguous Request
Investigate the current system around [problem]. Identify missing decisions, ask focused questions, then draft a specification with explicit non-goals and verification criteria.
Plan a System Migration
Plan the migration from [current state] to [target state]. Cover architecture deltas, data flows, sequencing, dependencies, compatibility, verification, and rollback.
Assess Second-Order Effects
Create an advanced change specification for [proposal]. Trace downstream effects, failure modes, operational risks, boundary constraints, phased delivery, acceptance tests, and rollback triggers.
Best Practices
- Provide the problem, affected systems, constraints, and relevant Gjalla project context.
- Resolve decisions that change the technical approach before approving the specification.
- Make every behavioral requirement observable and pair it with a verification method.
Avoid
- Do not approve a specification that assumes undocumented architecture or missing dependencies.
- Do not combine goals, implementation details, and verification into vague narrative paragraphs.
- Do not omit rollback planning for changes that affect production data or shared services.
Frequently Asked Questions
What does this skill produce?
It produces a structured change specification covering the problem, scope, requirements, technical approach, verification, dependencies, and rollback.
Does it require Gjalla?
Yes. Its intended workflow uses Gjalla CLI or MCP to retrieve project context and create the canonical specification.
Will it implement the feature?
No. It prepares the approved plan before implementation begins.
Can it use Claude Plan or another plan format?
Yes. It can present an alternative planning format, then record approved information in a Gjalla specification.
When should I use it?
Use it before non-trivial features, migrations, architectural changes, or work with important dependencies and rollback requirements.
How does it handle missing information?
It researches available specifications and source code, then asks focused questions that affect the proposed solution.