Skills context-driven-development
📦

context-driven-development

Content revision r2 Safe ⚙️ External commands

Build Projects with Managed Development Context

Scattered project knowledge creates inconsistent AI output and slows team decisions. This skill organizes product, technical, workflow, and delivery context into maintained project artifacts.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "context-driven-development" from https://skillstore.io/skills/sickn33-context-driven-development.md and its manifest at https://skillstore.io/api/skills/sickn33-context-driven-development/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.

Markdown detail GET /skills/sickn33-context-driven-development.md Signed manifest GET /api/skills/sickn33-context-driven-development/manifest Signed lockfile GET /api/skills/sickn33-context-driven-development/lockfile

Test it

Using "context-driven-development". We added PostgreSQL and completed team invitations. Which context should change?

Expected outcome:

  • Update tech-stack.md with the PostgreSQL version, rationale, configuration, and operational constraints.
  • Update product.md to mark team invitations as implemented and record any scope changes.
  • Update the completed track and tracks.md with final status and completion details.

Using "context-driven-development". Review this project before a new authentication track.

Expected outcome:

The review flags an outdated dependency list, missing authentication acceptance criteria, and an unresolved deployment constraint. Implementation waits for stakeholder confirmation.

Using "context-driven-development". Prepare a context handoff for the next development session.

Expected outcome:

  • Record completed tasks and the current stopping point in plan.md.
  • Document unresolved decisions, blockers, and required stakeholder responses.
  • Update tracks.md when the work status changed.

Security Audit

Safe
v5 • 7/23/2026 Open versioned report

All six external-command findings are Markdown formatting or fixed Conductor slash-command references, with no shell, dynamic input, or executable code. The reconnaissance finding is ordinary anti-pattern guidance; no prompt injection, exfiltration intent, or other semantic security issue was found.

1
Files scanned
405
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (6)
SKILL.md:23 SKILL.md:192 SKILL.md:207 SKILL.md:247-266 SKILL.md:266-270 SKILL.md:270-384
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 View Audit History →
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.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-context-driven-development/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-context-driven-development/security.svg)](https://skillstore.io/skills/sickn33-context-driven-development?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-context-driven-development?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-context-driven-development/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-context-driven-development.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). context-driven-development security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-context-driven-development/audits/5

BibTeX citation

@techreport{sickn33-sickn33-context-driven-development-2026, author = {sickn33}, title = {context-driven-development security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-context-driven-development/audits/5}, 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: "context-driven-development security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-context-driven-development/audits/5" identifiers: - type: other value: "skillstore:sickn33-context-driven-development:audit:5" description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score
wshobson Recommended

wshobson-context-driven-development

Skillstore Score 81
Evidence Confidence High
Skillstore usage 13
Updated

2026-08-21

sickn33 Current

sickn33-context-driven-development

Skillstore Score 78
Evidence Confidence High
Skillstore usage 12
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Establish a new project context

Create a shared foundation for product goals, technology choices, team practices, and planned work before implementation begins.

Document an existing codebase

Extract current patterns into structured artifacts, then review differences between actual and desired practices.

Improve team continuity

Maintain track status, decisions, and session handoffs so contributors can resume work with consistent context.

Try These Prompts

Create core context 
Help me define product.md, tech-stack.md, and workflow.md for [project]. Ask for missing goals, constraints, users, technologies, and quality requirements.
Audit context freshness 
Review [context documents] against [recent changes]. Identify stale statements, conflicts, missing decisions, and specific updates required before implementation.
Plan a feature track 
Using [product context], [technical context], and [workflow], draft a specification and phased plan for [feature]. Include acceptance criteria, dependencies, and validation.
Reconcile brownfield context 
Analyze [repository observations] and [existing context]. Separate confirmed patterns from assumptions, identify contradictions, and propose prioritized artifact updates with stakeholder questions.

Best Practices

  • Read current context artifacts before drafting specifications or implementation plans.
  • Update related documents together when product scope, dependencies, workflow rules, or track status changes.
  • Confirm extracted brownfield assumptions with stakeholders before treating them as canonical context.

Avoid

  • Do not scatter the same decision across multiple documents without a canonical source.
  • Do not let generated context replace repository evidence or stakeholder confirmation.
  • Do not expand context with details that do not influence decisions, behavior, or validation.

Frequently Asked Questions

What does this skill produce?
It guides creation and maintenance of product, communication, technology, workflow, and track context documents.
Does it require Conductor?
The guidance uses Conductor concepts and commands. You can adapt the artifact model, but slash commands require a compatible environment.
Can it analyze an existing repository?
It describes a brownfield process for extracting patterns. Repository access and analysis still depend on the active AI tool and permissions.
When should context documents be updated?
Update them when product goals, dependencies, infrastructure, team practices, features, or track status change.
How does it support multiple sessions?
It defines start, end, and interruption routines that record active work, decisions, blockers, and next steps.
Does maintained context guarantee correct code?
No. Context improves alignment, but implementation still requires testing, environment validation, security review, and stakeholder approval.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/context-driven-development

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

7 downloads · 119 views

File structure

📄 SKILL.md

More from sickn33

View all

Related Skills

View all