Skills gjalla-breakdown
📦
gjalla-breakdown
Content revision r1 Safe
Break Features Into Implementation Waves
Large feature specifications can be difficult to sequence and track. This skill creates dependency-ordered waves of small tasks with files and acceptance checks.
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-breakdown" from https://skillstore.io/skills/gjalla-gjalla-breakdown.md and its manifest at https://skillstore.io/api/skills/gjalla-gjalla-breakdown/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-breakdown". Add email verification to account registration.
Expected outcome:
- Wave 1: Add verification fields and migration, with schema checks as acceptance criteria.
- Wave 2: Create token generation and delivery tasks that depend on the schema update.
- Wave 3: Add verification endpoints, user interface changes, tests, and documentation.
Using "gjalla-breakdown". Add saved dashboard filters for signed-in users.
Expected outcome:
- W1-T1: Define stored filter data and persistence behavior.
- W2-T1: Add service operations after the data model is available.
- W2-T2: Build interface controls in parallel with service integration tests.
- W3-T1: Complete end-to-end verification and documentation.
Security Audit
Safev1 • 8/11/2026 Open versioned report
The single static finding is a false positive. SKILL.md contains planning guidance only, with no system reconnaissance, executable code, external commands, or prompt injection.
1
Files scanned
30
Lines analyzed
0
Review items
0
False positives ignored
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-breakdown/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/gjalla-gjalla-breakdown?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/gjalla-gjalla-breakdown?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/gjalla-gjalla-breakdown/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/gjalla-gjalla-breakdown.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-breakdown security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/gjalla-gjalla-breakdown/audits/1BibTeX citation
@techreport{gjalla-gjalla-gjalla-breakdown-2026,
author = {gjalla},
title = {gjalla-breakdown security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/gjalla-gjalla-breakdown/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-breakdown 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-breakdown/audits/1"
identifiers:
- type: other
value: "skillstore:gjalla-gjalla-breakdown: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 Feature Implementation
Convert an approved specification into sequenced tasks that are easy to assign, implement, and verify.
Coordinate Parallel Work
Identify independent tasks that multiple contributors can complete during the same implementation wave.
Prepare Agent Execution
Create a structured implementation plan with clear files, dependencies, and acceptance checks for coding agents.
Try These Prompts
Create a Basic Breakdown
Break this feature specification into dependency-ordered waves. Give each task an ID, description, files, dependencies, and acceptance check: [specification]
Plan With Repository Context
Review this specification and repository context. Produce implementation waves with tasks touching one or two files each: [specification and repository context]
Optimize Parallel Delivery
Break down this specification for parallel delivery. Minimize dependencies within each wave and include tests, documentation, and verification: [specification]
Resolve a Complex Dependency Plan
Create a wave plan for this complex feature. Explain dependencies, flag uncertain file ownership, and split the work if it exceeds 20 tasks: [specification]
Best Practices
- Provide the approved specification and relevant repository context before requesting a breakdown.
- Keep each task small enough to produce a focused, reviewable change.
- Review file paths, dependencies, and acceptance checks before implementation begins.
Avoid
- Do not use vague requirements that omit expected behavior or technical constraints.
- Do not combine unrelated modules into one large task without a clear dependency reason.
- Do not treat tasks within one wave as parallel when they depend on each other.
Frequently Asked Questions
What input does this skill need?
Provide a written feature specification or agent plan with behavioral requirements and expected technical changes.
What does each task include?
Each task includes an ID, description, exact file paths, dependencies, acceptance criteria, and a completion marker.
How are waves ordered?
Waves are sequential. Tasks within one wave should be independent and suitable for parallel work.
Does the skill implement the plan?
No. It creates the breakdown but does not edit files, run commands, or complete tasks.
How large should a breakdown be?
The guidance recommends fewer than 20 tasks. Split larger features into multiple specifications.
Does the breakdown include testing and documentation?
Yes. The skill explicitly includes tests, verification, documentation, and other completion work.