conductor-new-track
Create Conductor Tracks With Specs and Plans
New engineering work often starts without clear scope or acceptance criteria. This skill gathers inputs and produces Conductor specs, plans, metadata, and track links.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "conductor-new-track" from https://skillstore.io/skills/sickn33-conductor-new-track.md and its manifest at https://skillstore.io/api/skills/sickn33-conductor-new-track/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 "conductor-new-track". Create a feature track for team-level notification preferences.
Expected outcome:
- A classified feature track with summary, user story, acceptance criteria, dependencies, and scope boundaries.
- A phased implementation plan with verification after each phase.
- A completion note that lists the generated Conductor files.
Using "conductor-new-track". Create a bug track for export jobs timing out.
Expected outcome:
A bug-focused spec covering reproduction steps, expected behavior, actual behavior, affected areas, and a repair plan.
Using "conductor-new-track". Create a refactor track for simplifying checkout state management.
Expected outcome:
- A refactor track that records motivation, success criteria, risks, and phased implementation work.
- A metadata record and track index entry for Conductor navigation.
Security Audit
SafeAll static external command alerts are false positives caused by markdown backticks, code fences, and example paths in SKILL.md. The path traversal and network reconnaissance alerts are also false positives: they are relative documentation links and a progress heading, not dangerous behavior. No prompt injection or malicious intent was found.
Risk Factors
โ๏ธ External commands (66)
๐ Filesystem access (2)
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/sickn33-conductor-new-track/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-conductor-new-track?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-conductor-new-track?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-conductor-new-track/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-conductor-new-track.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
sickn33. (2026). conductor-new-track security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-conductor-new-track/audits/4BibTeX citation
@techreport{sickn33-sickn33-conductor-new-track-2026,
author = {sickn33},
title = {conductor-new-track security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-conductor-new-track/audits/4},
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: "conductor-new-track security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/sickn33-conductor-new-track/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-conductor-new-track:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Feature Planning
Product engineers can turn a feature idea into a reviewed spec and phased plan.
Bug Fix Intake
Support engineers can capture reproduction steps, expected behavior, affected areas, and a repair plan.
Refactor Coordination
Technical leads can document motivation, risks, success criteria, and verification work before refactoring.
Try These Prompts
Create a new feature track for adding saved searches to the dashboard.
Create a bug track for login redirects failing after password reset. Ask me one question at a time.
Create a refactor track for separating billing logic from account settings. Include risk questions and verification steps.
Create a chore track for migrating analytics events. Use Conductor context, capture dependencies, define out-of-scope work, and produce a phased plan.
Best Practices
- Review generated spec and plan text before creating files.
- Keep each track focused on one feature, bug, chore, or refactor.
- Use acceptance criteria and verification tasks that can be checked independently.
Avoid
- Starting a track before Conductor context files exist.
- Combining unrelated feature and refactor work in one track.
- Skipping the review steps and accepting incomplete scope.
Frequently Asked Questions
What does this skill create?
Does it write application code?
Can it handle bugs?
Does it require Conductor setup?
How does it choose a track ID?
Can I edit the generated spec or plan?
Developer Details
Author
sickn33License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/conductor-new-trackRef
01171b582d636c013315c5e0d969c64f8d9cdff2
Maintenance freshness
7/18/2026
Usage
6 downloads ยท 96 views
File structure
๐ SKILL.md