Create a team configuration Markdown file via guided interview.
npx skills add https://github.com/crewrig/crewrig --skill init-team-crewrig
Please help me install this Agent Skill. Skill: init-team Source: https://github.com/crewrig/crewrig/tree/main/artifacts/core/skills/init-team Command: npx skills add https://github.com/crewrig/crewrig --skill init-team-crewrig
This Skill helps adopters create a new per-team configuration file without guessing the required structure, sections, or safeguards. It guides the user through collecting the right team details and prevents accidental overwrites of existing files.
config/teams/<TEAM>.md format.Use the init-team skill to help me create a new team profile for Atlas and generate the correct config/teams/ATLAS.md file.
High-intent search queries and answers about installing and using this skill.
You create a team configuration file through a guided interview that captures the mission, technology stack, and development practices, then writes a conformant Markdown profile to the config/teams directory.
A per-team context profile is a Markdown file that captures core team details like mission and stack, with optional enrichment sections for rituals, collaboration norms, documentation, issue tracking, and key contacts.
To prevent accidental overwrites when adding team context files, the generation process detects filename collisions and requires an explicit user decision before replacing any existing configuration.
Yes, you can include operational sections like issue tracking and collaboration norms in your team profile through optional enrichment during the guided interview process.
The best way to capture development practices and technology stack details is a conversational guided interview that prompts for specific team information and generates a structured Markdown file.
crewrigCreate expertise role markdown files under config/expertise via guided interview.
cvillamarp-lgtmDesign named, templated team rituals using the Golden Rituals framework.
javiarmestoRecord architectural decisions as timestamped markdown files in project directories.
nweiiAnalyze file content and metadata to propose consistent rename plans.