template-feature-addition

Solid

End-to-end feature work across src/, scripts/, tests/, manuscript, and docs for the Research Project Template. USE WHEN adding a pipeline-visible feature, new analysis stage, manuscript-facing output, or cross-layer integration — even without feature_addition prompt.

Data & Documents 18 stars 1 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 81/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Feature addition ## Natural invoke - "Add convergence plotting to template_code_project end-to-end" - "New infrastructure gate wired into health CLI + tests + docs" - "Feature: export manifest JSON from analysis stage" ## Inputs to confirm - **Feature description** — user-facing behavior. - **Layer** — infrastructure vs project (see [code-development](../code-development/SKILL.md)). - **Project** — if project layer. ## Workflow 1. **Design** — logic in `src/` or `infrastructure/`; script coordinates only. 2. **Implement** — src modules first (TDD: tests alongside). 3. **Orchestrate** — `projects/<n>/scripts/` or root `scripts/` stage hook if pipeline-visible. 4. **Manuscript** — figures/data paths, `{{VARIABLE}}` generated variables if numbers appear in prose. 5. **Docs** — AGENTS.md/README at affected dirs; no roster duplication. 6. **Verify** — project or infra tests; optional `./run.sh --project <n> --core-only` slice. ## Deliverables - File list by layer - Test + pipeline verification commands and exit codes ## Verification commands ```bash uv run python scripts/pipeline/stage_01_test.py --project <project> uv run python scripts/runner/execute_pipeline.py --project <project> --core-only ``` ## When NOT to use - **Single function, no pipeline/manuscript touch** → [code-development](../code-development/SKILL.md) - **Refactor without new behavior** → [refactoring](../refactoring/SKILL.md) ## References Checklist: [references/checklist.md](references/chec...

Details

Author: docxology
Repository: docxology/template
Created: 11 months ago
Last Updated: today
Language: Python
License: Apache-2.0

Integrates with

Ollama · AI pytest · Testing

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

template-code-development

Standards-compliant code for the Research Project Template — infrastructure or project src/, thin orchestrators, type hints, no mocks. USE WHEN implementing an algorithm, utility, analysis method, optimizer, new module in projects/*/src or infrastructure/, or user says add code following template architecture — even without docs/prompts. Not for end-to-end feature spanning manuscript + pipeline (use template-feature-addition).

18 Updated today

docxology

Code & Development Solid

feature

Add a feature to an existing project with a full sprint. Skips /think diagnostic, goes straight to planning. Use when the user knows what they want and the project already exists. Triggers on /feature.

1 Updated yesterday

Jihadyip286

AI & Automation Listed

add-feature

Add a new conforming vertical-slice feature (Screen + ViewModel + UseCase + Repository + spec + tests + golden tree + nav route + DI wiring) to this Compose Multiplatform app, cloned deterministically from the project's configured exemplar feature (qa/approvals.json's exemplarFeature — `home` by default). Use this when the user wants to "add a feature", "add a screen with data", "scaffold a feature", "create a new screen backed by a repository", "add a list screen", or names a new domain noun they want a screen for (e.g. "add a Favorites feature", "I need a Bookmarks screen"). Works with NO create-cmp plugin installed — the stamper (`qa/scaffold-feature.mjs`) and this skill both ship inside the generated project.

0 Updated 3 days ago

kvdm-co-pilot